aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces/python/pgdb.py
Commit message (Collapse)AuthorAge
* remove python module, as its moved to http://www.pygresql.orgMarc G. Fournier2003-08-01
|
* Correction to last patch. As per the DB-API spec, we need to return NoneD'Arcy J.M. Cain2003-01-08
| | | | here, not -1.
* Remove typprtlen from getdescr() as it is not available in 7.3. Return -1 forD'Arcy J.M. Cain2002-12-04
| | | | that field so that existing programs don't break.
* I'm sending you a small patch to pgdb.py module. ThisD'Arcy J.M. Cain2002-11-25
| | | | | | | | | | | | | | raises pgdb.DatabaseError when any of the fetch* methods was invoked but previous call to execute* did not produce any result set or no call was issued yet. Also, raises pgdb.NotSupportedError when .nextset() is invoked, instead of NameError. This behaviour complies with DB-API 2.0. Thanks for your work! Timur Irmatov.
* This patch implements FOR EACH STATEMENT triggers, per my email toBruce Momjian2002-11-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -hackers a couple days ago. Notes/caveats: - added regression tests for the new functionality, all regression tests pass on my machine - added pg_dump support - updated PL/PgSQL to support per-statement triggers; didn't look at the other procedural languages. - there's (even) more code duplication in trigger.c than there was previously. Any suggestions on how to refactor the ExecXXXTriggers() functions to reuse more code would be welcome -- I took a brief look at it, but couldn't see an easy way to do it (there are several subtly-different versions of the code in question) - updated the documentation. I also took the liberty of removing a big chunk of duplicated syntax documentation in the Programmer's Guide on triggers, and moving that information to the CREATE TRIGGER reference page. - I also included some spelling fixes and similar small cleanups I noticed while making the changes. If you'd like me to split those into a separate patch, let me know. Neil Conway
* Small patch to correct the default arraysize associatedBruce Momjian2002-06-03
| | | | | | | | with the Cursor object's fetchmany() method. The API and inline documentation state that the default is 1. It currently defaults to 5. Patrick Macdonald
* Remove the last traces of datatypes datetime and timespan.Tom Lane2002-05-03
|
* pgdb.connect() seems to be broken on Python 2.0.1 (which ships withBruce Momjian2002-04-24
| | | | | | | | | | | Slackware 8), and perhaps on other Pythons, haven't checked. Something in the _pg.connect() call isn't working. I think the problem stems from the fact that 'host' is a named parameter of both _pg.connect and pgdb.connect, and so Python treats it as a variable assignment, not a named parameter. Uses non-named parameters. Andrew Johnson
* Back out python change, needs delay.Bruce Momjian2002-04-18
|
* Change docs to do 20! rather than larger.Bruce Momjian2002-04-18
|
* > I am backing out this patch. Please resubmit with this corrected. Thanks.Bruce Momjian2002-03-19
| | | | | | | | | | | | | | | | | > > I am running Python 1.5. Therein lies the problem... :) Since it appears you have the requirement of supporting old python versions, attached is just the pgdb.py part of the patch (with a fix for DateTime handling). It has the same functionality but certainly won't be quite as fast. Given the absence of _PyString_Join in python1.5, it's a pain to get the C variants working for all versions. The pgdb.py patch does leaves the hooks in, should someone wish to do the optimization at a later point. Elliot Lee
* Back out python patch:Bruce Momjian2002-03-05
| | | | | | | | Elliot Lee wrote: > This patch to the python bindings adds C versions of the often-used query > args quoting routines, as well as support for quoting lists e.g. > dbc.execute("SELECT * FROM foo WHERE blah IN %s", ([1,2,3],))
* This patch to the python bindings adds C versions of the often-usedBruce Momjian2002-03-05
| | | | | | | query args quoting routines, as well as support for quoting lists e.g. dbc.execute("SELECT * FROM foo WHERE blah IN %s", ([1,2,3],)) Elliot Lee
* Add bpchar to list of string types.D'Arcy J.M. Cain2001-06-15
| | | | Thanks to Steve McClure <smcclure@racemi.com> for the patch.
* I just noticed the beta comment. That's not actually true any moreD'Arcy J.M. Cain2001-04-12
| | | | so I removed it.
* Marc-Andre is changing where DateTime goes. This change allows the moduleD'Arcy J.M. Cain2001-03-30
| | | | | to work either way. Change submitted by Andrew Kuchling <akuchlin@mems-exchange.org>
* Correct indenting in _quote() function.D'Arcy J.M. Cain2001-03-30
| | | | Fix submitted by Andrew Kuchling <akuchlin@mems-exchange.org>
* Fix parameter handling.D'Arcy J.M. Cain2001-03-15
| | | | | Fix a bug where cs.execute('select %d + %d', (1, 2)) would get interpreted as cs.executemany('select %d + %d', (1, 2))
* Update to PyGreSQL 3.1:Bruce Momjian2000-11-10
| | | | | | | | | | | | | | | | | | | | | | | | | | Fix some quoting functions. In particular handle NULLs better. Use a method to add primary key information rather than direct manipulation of the class structures. Break decimal out in _quote (in pg.py) and treat it as float. Treat timestamp like date for quoting purposes. Remove a redundant SELECT from the get method speeding it, and insert since it calls get, up a little. Add test for BOOL type in typecast method to pgdbTypeCache class. (tv@beamnet.de) Fix pgdb.py to send port as integer to lower level function (dildog@l0pht.com) Change pg.py to speed up some operations Allow updates on tables with no primary keys. D'Arcy J.M. Cain
* Update for PyGreSQL 3.0, from D'Arcy J.M. CainBruce Momjian2000-10-02
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-25 07:49:14 +0000