Re: DB API 2.0 and transactions

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Magnus Lycka wrote:

> Another option would be to investigate if any of the other postgreSQL
> drivers have a more correct behaviour. The non-standard behaviour that
> you describe it obvious from the pgdb source. See:
> http://www.pygresql.org/cvsweb.cgi/pygresql/module/pgdb.py?rev=1.27

fwiw psycopg 1.1.18 has the correct behavior (as usual).

I can add this test to the DB-API 2.0 Anal Compliance Test Suite if we want,
although it sounds like it is only an issue with PostgreSQL drivers.

- --
Stuart Bishop <stuart@xxxxxxxxxxxxxxxx>
http://www.stuartbishop.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCsk3oAfqZj7rGN0oRAjHAAJ4kQzxJXFW6hX6Q1t896fMzT0EUjACgkBhw
X4wB17+4FwO9TsKpiIBJB50=
=mYfn
-----END PGP SIGNATURE-----
.