Changeset 1015


Ignore:
Timestamp:
Jun 7, 2019, 1:16:43 PM (6 weeks ago)
Author:
cito
Message:

Fix several typos in the documentation.

As suggested by Justin Pryzby on the mailing list.

Location:
trunk
Files:
6 edited

Legend:

Unmodified
Added
Removed
  • trunk/docs/contents/changelog.rst

    r1011 r1015  
    2626    - New methods query.dictiter(), query.namediter() and query.scalariter()
    2727      returning the same values as query.dictresult(), query.namedresult()
    28       and query.salarresult(), but as iterables instead of lists. This avoids
     28      and query.scalarresult(), but as iterables instead of lists. This avoids
    2929      creating a Python list of all results and can be slightly more efficient.
    3030    - Removed pg.get/set_namedresult. You can configure the named tuples
  • trunk/docs/contents/pg/adaptation.rst

    r962 r1015  
    163163In real world examples you will rarely have to cast your parameters like that,
    164164since in an INSERT statement or a WHERE clause comparing the parameter to a
    165 table column the data type will be clear from the context.
     165table column, the data type will be clear from the context.
    166166
    167167When binding the parameters to a query, PyGreSQL not only adapts the basic
     
    175175    [[1, 2], [3, 4]]
    176176
    177 Note that again we only need to cast the array parameter or use inline
    178 parameters because this simple query does not provide enough context.
     177Note that again we need to cast the array parameter or use inline parameters
     178only because this simple query does not provide enough context.
    179179Also note that the query gives the value back as Python lists again.  This
    180180is achieved by the typecasting mechanism explained in the next section.
  • trunk/docs/contents/pg/db_wrapper.rst

    r979 r1015  
    494494If you set *inline* to True or don't pass any parameters, the command string
    495495can also include multiple SQL commands (separated by semicolons). You will
    496 only get the return value for the last command in this case.
    497 
    498 Note that the adaption and conversion of the parameters causes a certain
     496only get the result for the last command in this case.
     497
     498Note that the adaptation and conversion of the parameters causes a certain
    499499performance overhead. Depending on the type of values, the overhead can be
    500500smaller for *inline* queries or if you pass the types of the parameters,
  • trunk/docs/contents/pg/module.rst

    r992 r1015  
    446446
    447447.. versionchanged:: 5.0
    448     Arrays had been always returned as text strings only in earlier versions.
     448    Arrays had been always returned as text strings in earlier versions.
    449449
    450450get/set_bytea_escaped -- whether bytea data is returned escaped
  • trunk/docs/contents/pg/query.rst

    r985 r1015  
    8484.. versionadded:: 5.1
    8585
    86 namedresult/namediter -- get query values a named tuples
    87 --------------------------------------------------------
     86namedresult/namediter -- get query values as named tuples
     87---------------------------------------------------------
    8888
    8989.. method:: Query.namedresult()
  • trunk/pg.py

    r989 r1015  
    19401940
    19411941        This creates a prepared statement for the given command with the
    1942         the given name for later execution with the query_prepared() method.
     1942        given name for later execution with the query_prepared() method.
    19431943
    19441944        The name can be empty to create an unnamed statement, in which case
Note: See TracChangeset for help on using the changeset viewer.