| From: | Jonathan Rogers <jrogers(at)socialserve(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [RFC] ideas for a new Python DBAPI driver (was Re: libpq test suite) |
| Date: | 2013-02-14 17:18:08 |
| Message-ID: | 511D1C50.3000904@socialserve.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A number of the described features sound quite useful. Is it not
practical to extend an existing library such as psycopg2? What method
will you use to call libpq functions? As you are no doubt aware,
psycopg2 uses the traditional CPython API but there is a fork which uses
ctypes instead, enabling it to work with CPython and Pypy.
Manlio Perillo wrote:
> For my Python DBAPI2 PostgreSQL driver I plan the following optimizations:
>
> 2) when the driver detects a Python string is being sent to the
> database, use binary format.
What exactly do you mean by "Python string"?
- --
Jonathan Ross Rogers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlEdHFAACgkQVmXTv6uMqqOlzgCgxcGtjwFqK1AMKAED9rK5YSOa
3AMAoJhw4197HPBrjpxG/iSLK43B1B3j
=RnaP
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2013-02-14 17:18:41 | Re: 9.2.3 crashes during archive recovery |
| Previous Message | Robert Haas | 2013-02-14 17:00:33 | Re: sql_drop Event Trigger |