source: trunk/docs/future.txt @ 298

Last change on this file since 298 was 298, checked in by cito, 13 years ago

Updated docs

File size: 1.6 KB
Line 
1==========================
2PyGreSQL future directions
3==========================
4
5
6To Do
7-----
8
9- Support PQescapeStringConn and PQescapeByteaConn
10  (see also http://www.postgresql.org/docs/techdocs.49)
11- Use PQescapeStringConn in the _quote() function of pg and pgdb.
12- Support composite primary keys
13  (see http://mailman.vex.net/pipermail/pygresql/2006-May/001688.html)
14- The DB-API module needs docstrings and external documentation.
15- Create separate unit tests for _pg, pg and pgdb.
16- The large object and direct access functions need much more attention.
17- An update query should return the number of rows affected.
18- The C module needs to be cleaned up and redundant code merged.
19- The fetch method should use real cursors.
20
21
22Proposed Patches
23----------------
24
25- Notice handling
26  (http://mailman.vex.net/pipermail/pygresql/2005-November/001530.html)
27
28
29Wish List
30---------
31
32- Make SQLSTATE error codes available.
33- Make use of PQexecParams() and PQprepare(). This could speed up
34  executemany() and allow retrieving binary data directly by setting
35  the resultFormat parameter to one.
36- Users should be able to register their own types with _pg.
37- I would like a new method that returns a dictionary
38  of dictionaries from a SELECT.
39- Add support for persistent and pooled connections
40  that can be used in multi-threaded environments (we could simply
41  (add http://www.webwareforpython.org/DBUtils to the distribution).
42- Make PyGreSQL thread-safe on the connection level.
43- The API documentation could be created with Epydoc.
44- Write a tutorial for beginners and advanced use.
45- More and better documented examples.
Note: See TracBrowser for help on using the repository browser.