Christoph Zwerschke

We should integrate support for i18n and l10n or at least document how to handle this in Webware using existing tools.

Separate more clearly and systematically which messages are printed to stdout and which to stderr, or even better: Make use of the logging module instead of conditional print statements with...

Sprinkled throughout the code are comments tagged with @@ which are hopefully accompanied by a date and someone's initials. These comments represent things to be done. The double at-sign (@@)...

Support optional cursor and connection attribute "messages"

1

The ​DBAPI2 PEP 249 proposes an optional optional cursor and connection attribute "messages". We should look into that. (copied from Trac ticket 19, created 2010-09-12)

Make PyGreSQL thread-safe on the connection level

1

Check whether the treadsafety of PyGreSQL can/should be improved. (copied from Trac ticket 24, created 2010-09-12)

Consider avoiding encoding/decoding bytea in queries

1

Currently, when executing queries that contain `bytea` values on input or output, these are encoded from bytes and decoded to bytes on the level of the pgdb module and the...

The pgdb cursor object should optionally be a real database cursor

3

It should be possible to create "real" (server side) cursors usind the `pgdb.Connection.cursor()` method. It would make sense to add an optional `name` parameter that would be used as the...

Currently, connections in the classic and DB API 2 modules are made with `PQsetdbLogin` which only allows a limited number of parameters. Additional parameters must be sent as connection string...

In the `pgdb` module and the `query_formatted()` and higher level methods of the `pg` module such as `update()`, input parameters are adapted automatically, e.g. converting Python lists to PostgreSQL arrays....

PyGreSQL has some preprocessor macros such as `SSL_INFO` that control which features are enabled. Some features may be disabled when they are not supported by the installed PostgreSQL version. The...