source: trunk/docs/future.txt @ 626

Last change on this file since 626 was 626, checked in by cito, 4 years ago

Ticket mentioned in future.txt has been closed

  • Property svn:keywords set to Author Date Id Revision
File size: 2.1 KB
2PyGreSQL future directions
5This list has been closed since tasks are now managed with the PyGreSQL
6tracker that can be found at
7(ticket numbers have been added below):
9To Do
12- Add docs for the pgdb module (everything specific to PyGreSQL) (#5).
13- The fetch method should use real cursors (#7).
14- The C module needs to be cleaned up and redundant code merged,
15  and should get its own unit test module (#8).
16- Clean up and merge it with (#9).
17- The test suite for the classic module should also check that quoted
18  mixed-case identifiers can be used everywhere - currently they can't.
19  Improve accordingly, adding quotes etc. as needed (#10).
20- What shall we do with the "tutorial" directory - it's rather a tutorial
21  for Postgres/SQL than for PyGreSQL, it's using only the query method from
22  the classic pg module and no other PyGreSQL functionality, it's rather
23  a demo than a tutorial (#11)?
25Wish List
28- Make use of PQexecParams() and PQprepare(). This could speed up
29  executemany() and allow retrieving binary data directly by setting
30  the resultFormat parameter to one (#16).
31- Enhance cursor.description attribute, delivering more information
32  available with PQfmod() or PQftable() for instance (#17).
33- Support optional "errorhandler" extension (#18).
34- Support optional cursor and connection attribute "messages" (#19).
35- Users should be able to register their own types with _pg (#21).
36- pg has now got a new method namedresult() that returns named tuples.
37  pgdb should also support named tuples, maybe via a row_factory attribute
38  on the connection, similar to sqlite3 (see #22).
39- New methods in the classic module, similar to getresult() and
40  dictresult(), but returning dictionaries of rows instead of lists
41  of rows (with primary key or oids as keys) (#23).
42- Make PyGreSQL thread-safe on the connection level (#24).
43- The API documentation could be created with Epydoc or Sphinx (#4).
44- Write a tutorial for beginners and advanced use (#11).
45- More and better documented examples (#4, #5, #11).
Note: See TracBrowser for help on using the repository browser.