aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces/python
Commit message (Collapse)AuthorAge
* Back patch bug fix to quote function.D'Arcy J.M. Cain2003-02-27
|
* Back-patch typprtlen fix, two other minor post-7.3 fixes.Tom Lane2003-01-21
|
* Move PyGreSQL usage documentation from README into DocBook. Some otherPeter Eisentraut2002-09-23
| | | | editing.
* pgindent run.Bruce Momjian2002-09-04
|
* This is a quick patch to fix a crash in pgquery_dictresult() introducedBruce Momjian2002-08-28
| | | | | | | recently. I just ran into it while running a set of python test scripts, and I'm not sure who the normal maintainer is for interfaces/python. John Nield
* This fixes some text as well as enforces the use of "drop table cascade"Bruce Momjian2002-08-15
| | | | | | | since we moved from an implicate to explicate implementation. Greg Copeland
* Well, that certainly appeared to be very straight forward. pg.py andBruce Momjian2002-08-15
| | | | | | | | | | | syscat.py scripts were both modified. pg.py uses it to cache a list of pks (which is seemingly does for every db connection) and various attributes. syscat uses it to walk the list of system tables and queries the various attributes from these tables. In both cases, it seemingly makes sense to apply what you've requested. Greg Copeland
* http://archives.postgresql.org/pgsql-bugs/2002-06/msg00086.php and neverBruce Momjian2002-08-15
| | | | | | | | | | | | | | | | | | | | saw a fix offered up. Since I'm gearing up to use Postgres and Python soon, I figured I'd have a hand at trying to get this sucker addressed. Apologies if this has already been plugged. I looked in the archives and never saw a response. At any rate, I must admit I don't think I fully understand the implications of some of the changes I made even though they appear to be straight forward. We all know the devil is in the details. Anyone more knowledgeable is requested to review my changes. :( I also updated the advanced.py script in a somewhat nonsensical fashion to make use of an int8 field in an effort to test this change. It seems to run okay, however, this is by no means an all exhaustive test. So, it's possible that a bumpy road may lay ahead for some. On the other hand...overflows (hopefully) previously lurked (long -> int conversion). Greg Copeland
* 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
* Fix typo in usage instructions.Tom Lane2002-05-03
|
* 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
|
* Restructure representation of aggregate functions so that they have pg_procTom Lane2002-04-11
| | | | | | | | | | entries, per pghackers discussion. This fixes aggregates to live in namespaces, and also simplifies/speeds up lookup in parse_func.c. Also, add a 'proimplicit' flag to pg_proc that controls whether a type coercion function may be invoked implicitly, or only explicitly. The current settings of these flags are more permissive than I would like, but we will need to debate and refine the behavior; for now, I avoided breaking regression tests as much as I could.
* Fox for old python PyMem_DEL, was PyMem_Del,Bruce Momjian2002-03-29
|
* Fix '#' commant to be proper C comment.Bruce Momjian2002-03-29
|
* Further changes following discussion on INTERFACES mailing list:D'Arcy J.M. Cain2002-03-26
| | | | | - Use PyObject_Del() rather than macro version - Check version and drop back to PyMem_Del() for older systems.
* PyGreSQL causes a segfault when used with a Python executable that wasD'Arcy J.M. Cain2002-03-20
| | | | | compiled with --with-pymalloc. This change fixes that. Thanks to Dave Wallace <dwallace@udel.edu>
* Bump version number to match tree.D'Arcy J.M. Cain2002-03-19
|
* Fix name in comments and add info about this module's place in PyGreSQL.D'Arcy J.M. Cain2002-03-19
|
* > 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
* revert last changePeter Eisentraut2001-12-13
|
* Bump version to 3.3. Mostly this is because there is some confusion aboutD'Arcy J.M. Cain2001-12-03
| | | | | | | the latest version and I wanted to make sure that there was a clean release. I also change the build files as I discussed in my letter of Nov 6, 2001. At the time I was asked to hold off until after the release.
* A bunch of small doco updates motivated by scanning the comments onTom Lane2001-11-19
| | | | the interactive docs.
* New pgindent run with fixes suggested by Tom. Patch manually reviewed,Bruce Momjian2001-11-05
| | | | initdb/regression tests pass.
* Version was 3.3 but last released version was 3.1. Setting to match restD'Arcy J.M. Cain2001-11-04
| | | | of the documentation in preparation for upcoming release.
* Note that PyGreSQL has been checked against Python 2.1 now.D'Arcy J.M. Cain2001-11-04
|
* The "%d", while syntactically correct, was confusing. Added a space toD'Arcy J.M. Cain2001-11-04
| | | | make it clearer that d was the argument to the format operator.
* Another pgindent run. Fixes enum indenting, and improves #endifBruce Momjian2001-10-28
| | | | spacing. Also adds space for one-line comments.
* pgindent run on all C files. Java run to follow. initdb/regressionBruce Momjian2001-10-25
| | | | tests pass.
* > This stops the interface from leaking the row tuples (and thus theBruce Momjian2001-10-19
| | | | | | > results of every fetch). Stephen Robert Norris
* Python handle as string all int8 values from postgresql. This could beBruce Momjian2001-10-16
| | | | | | | | | | | | | | | view when using the aggregate function count() and function nextval that returns an int8 value, but in python is represented like string: >> db.query("select nextval('my_seq')").getresult() [('2',)] >> db.query("select count(*) from films").dictresult() [{'count': '120'}] Ricardo Caesar Lenzi
* Change the version. We are moving towards the next release.D'Arcy J.M. Cain2001-09-19
| | | | Fixed a nasty bug that messed up negative money amounts.
* Remove INV_ARCHIVE mention in python readme.Bruce Momjian2001-09-10
|
* Rename config.h to pg_config.h and os.h to pg_config_os.h, fix a number ofPeter Eisentraut2001-08-24
| | | | places that were including the wrong files.
* This patch fixes the well-known but unfixed bug that fetchone() always returnsBruce Momjian2001-08-16
| | | | | | | the first result in the DB-API compliant wrapper. It turned out that the bug was way down in the C code. Gerhard Häring
* Add prototypes to supress warnings.Bruce Momjian2001-07-11
|
* Support fake root install, separate build dir, dependency tracking, ourPeter Eisentraut2001-07-10
| | | | | | choice of compiler and flags, uninstall, and peculiar Python installation layouts for PyGreSql. Also install into site-packages now, as officially recommended. And pgdb.py is also installed now, used to be forgotten.
* Include catalog/pg_type.h instead of manually extracting the interestingPeter Eisentraut2001-06-22
| | | | oid values.
* Make sure that everything says version 3.2.D'Arcy J.M. Cain2001-06-20
|
* Add NUMERICOID to this script. This script can be run occasionally toD'Arcy J.M. Cain2001-06-20
| | | | | make sure that we are using the right #defines in pgmodule.c but the OIDs are never actually expected to change.
* Add bpchar to list of string types.D'Arcy J.M. Cain2001-06-15
| | | | Thanks to Steve McClure <smcclure@racemi.com> for the patch.
* Add missing comma.D'Arcy J.M. Cain2001-05-30
|
* Add NUMERICOID return type. Treat it as floating point for now. ThisD'Arcy J.M. Cain2001-05-27
| | | | | could be changed if we create a new Python type that matches it better but NUMERIC <==> FLOAT probably works fine for most cases.
* While changing Cygwin Python to build its core as a DLL (like Win32Bruce Momjian2001-05-25
| | | | | | | | | | | | | | | Python) to support shared extension modules, I have learned that Guido prefers the style of the attached patch to solve the above problem. I feel that this solution is particularly appropriate in this case because the following: PglargeType PgType PgQueryType are already being handled in the way that I am proposing for PgSourceType. Jason Tishler
* Back out, per Peter E.Bruce Momjian2001-05-25
| | | | | | | > > The attached patch changes src/interfaces/python/GNUmakefile to use the > > value of DESTDIR like the rest (or at least most) of the PostgreSQL > > makefiles. I found this problem when trying to package a pre-built > > Cygwin PostgreSQL distribution, but this problem is platform independent.
* The attached patch changes src/interfaces/python/GNUmakefile to use theBruce Momjian2001-05-25
| | | | | | | | | | | | | | | | | | | | value of DESTDIR like the rest (or at least most) of the PostgreSQL makefiles. I found this problem when trying to package a pre-built Cygwin PostgreSQL distribution, but this problem is platform independent. The problem manifests itself when one tries to install into a stagging area (e.g., to build a tarball) instead of a real install. In this case, pg.py and _pgmodule$(SO) still end up being installed in the configured prefix directory ignoring the value of DESTDIR. Unfortunately, this patch does not handle the case where PostgreSQL and Python are configured with different prefixes. Since the Python Makefile is automatically generated and does not use DESTDIR, I believe that this issue will be difficult to correct. If anyone has ideas on how to fix this issue, then I'm quite willing to rework the patch to take the suggestion into account. Jason Tishler
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-22 21:09:52 +0000