Changeset 371 for trunk/docs


Ignore:
Timestamp:
Nov 23, 2008, 6:29:48 AM (11 years ago)
Author:
cito
Message:

Updated docs. "insert/update ... returning" is already supported and only needed documentation.

Location:
trunk/docs
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • trunk/docs/future.txt

    r370 r371  
    3333---------
    3434
    35 - Support for the new insert/update ... returning ... feature
    36   (see http://jakub.fedyczak.net/post/10/).
    3735- Make SQLSTATE error codes available.
    3836- Make use of PQexecParams() and PQprepare(). This could speed up
    3937  executemany() and allow retrieving binary data directly by setting
    4038  the resultFormat parameter to one.
     39- Support .errorhandler extension.
    4140- Connection as context manager (see http://tinyurl.com/6j9cef).
    4241- Users should be able to register their own types with _pg.
    43 - I would like a new method that returns a dictionary
    44   of dictionaries from a SELECT.
    45 - Add support for persistent and pooled connections
    46   that can be used in multi-threaded environments
    47   or just add link to http://www.webwareforpython.org/DBUtils.
     42- New methods in the classic module, similar to getresult() and
     43  dictresult(), but returning dictionaries of rows instead of lists
     44  of rows (with primary key or oids as keys).
    4845- Make PyGreSQL thread-safe on the connection level.
    4946- The API documentation could be created with Epydoc.
  • trunk/docs/pg.txt

    r368 r371  
    444444  or delete statement, or an insert statement that did not insert exactly one
    445445  row in a table with OIDs, then the numer of rows affected is returned as a
    446   string. If it is a select statement that returns a result, this method returns
    447   a `pgqueryobject` that can be accessed via the `getresult()` or `dictresult()`
    448   method or simply printed. Otherwise, it returns `None`.
     446  string. If it is a statement that returns rows as a result (usually a select
     447  statement, but maybe also an "insert/update ... returning" statement), this
     448  method returns a `pgqueryobject` that can be accessed via the `getresult()`
     449  or `dictresult()` method or simply printed. Otherwise, it returns `None`.
    449450
    450451
  • trunk/docs/pgdb.txt

    r213 r371  
    2323provided by the `pgdb` module.
    2424
    25 `DB-API 2.0 <http://www.python.org/peps/pep-0249.html>`_
     25`DB-API 2.0 <http://www.python.org/dev/peps/pep-0249/>`_
    2626(Python Database API Specification v2.0)
    2727is a specification for connecting to databases (not only PostGreSQL)
     
    3131
    3232The authoritative programming information for the DB-API is availabe at
    33   http://www.python.org/peps/pep-0249.html
     33  http://www.python.org/dev/peps/pep-0249/
    3434
    35 A tutorial like introduction to the DB-API can be found at
     35A tutorial-like introduction to the DB-API can be found at
    3636  http://www2.linuxjournal.com/lj-issues/issue49/2605.html
    3737
  • trunk/docs/readme.txt

    r350 r371  
    185185compliant interface provided by the `pgdb` module.
    186186
    187 `DB-API 2.0 <http://www.python.org/peps/pep-0249.html>`_
     187`DB-API 2.0 <http://www.python.org/dev/peps/pep-0249/>`_
    188188(Python Database API Specification v2.0)
    189189is a specification for connecting to databases (not only PostGreSQL)
     
    192192The programming information is available in the files
    193193`pg.txt <pg.html>`_ and `pgdb.txt <pgdb.html>`_.
     194
     195Note that PyGreSQL is not thread-safe on the connection level. Therefore
     196we recommend using `DBUtils <http://www.webwareforpython.org/DBUtils>`
     197for multi-threaded environments, which supports both PyGreSQL interfaces.
    194198
    195199
Note: See TracChangeset for help on using the changeset viewer.