| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
compiled with --with-pymalloc. This change fixes that. Thanks to
Dave Wallace <dwallace@udel.edu>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
>
> 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
|
|
|
|
|
|
|
|
| |
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],))
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
the interactive docs.
|
|
|
|
| |
initdb/regression tests pass.
|
|
|
|
| |
of the documentation in preparation for upcoming release.
|
| |
|
|
|
|
| |
make it clearer that d was the argument to the format operator.
|
|
|
|
| |
spacing. Also adds space for one-line comments.
|
|
|
|
| |
tests pass.
|
|
|
|
|
|
| |
> results of every fetch).
Stephen Robert Norris
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Fixed a nasty bug that messed up negative money amounts.
|
| |
|
|
|
|
| |
places that were including the wrong files.
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
oid values.
|
| |
|
|
|
|
|
| |
make sure that we are using the right #defines in pgmodule.c but the
OIDs are never actually expected to change.
|
|
|
|
| |
Thanks to Steve McClure <smcclure@racemi.com> for the patch.
|
| |
|
|
|
|
|
| |
could be changed if we create a new Python type that matches it better
but NUMERIC <==> FLOAT probably works fine for most cases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
> > 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
there's no shared libpython. Test suite works as well. Also, add some
documentation.
|
|
|
|
| |
the way to handle this.
|
|
|
|
|
|
| |
properly on 64 bit systems.
Change submitted by Marc Poinot (Marc.Poinot@onera.fr)
|
|
|
|
| |
so I removed it.
|
|
|
|
|
| |
to work either way.
Change submitted by Andrew Kuchling <akuchlin@mems-exchange.org>
|
|
|
|
| |
Fix submitted by Andrew Kuchling <akuchlin@mems-exchange.org>
|
|
|
|
|
|
| |
Use Extension method from distutils.
Cleaned up mismatched indentation styles while I was at it.
|
| |
|
|
|
|
|
|
| |
PyGreSQL module when installing PostgreSQL.
Document the location of the WIN32 binaries.
|
| |
|
| |
|
|
|
|
|
| |
Fix a bug where cs.execute('select %d + %d', (1, 2)) would get interpreted
as cs.executemany('select %d + %d', (1, 2))
|
| |
|
|
|
|
|
|
| |
PostgreSQL.
Add notice that development has moved into the PostgreSQL tree.
|
|
|
|
| |
Add a test to avoid an exception in certain cases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
am talking with Thomas Lockhart about the idea of bringing the PyGreSQL
version number into alignment with PostgreSQL so this may change to 7.1
before the release.
I have added to the copyright to indicate that from now on the PostgreSQL
copyright will apply. If someone wants to make that clearer please do.
The existing copyrights need to stay there for now but if necessary I can
ask Pascal Andre if he agrees to a different wording.
Added reference to the Python DB-API 2.0 compliant API wrapper.
Added reference to the PyGreSQL mailing list.
|
|
|
|
|
| |
Changed the way that OID is retrieved on inserts. PQoidStatus appears
to be deprecated so I am using PQoidValue instead.
|