On Thursday 14 February 2013, Manlio Perillo wrote:
> Il 14/02/2013 14:06, Albe Laurenz ha scritto:
> > Manlio Perillo wrote:
> >> Sorry for the question, but where can I find the libpq test suite?
> >> I can not find it in the PostgreSQL sources; it seems that there are
> >> only some examples, in
On Fri, Feb 15, 2013 at 9:28 PM, Peter Eisentraut wrote:
> On 2/14/13 2:42 PM, Marko Tiikkaja wrote:
>>> I think the reason this doesn't work is that in order to prepare a query
>>> you need to know the parameter types, but you don't know that in Python,
>>> or at least with the way the DB-API wor
On 2/14/13 2:42 PM, Marko Tiikkaja wrote:
>> I think the reason this doesn't work is that in order to prepare a query
>> you need to know the parameter types, but you don't know that in Python,
>> or at least with the way the DB-API works. For example, if you write
>>
>> cur.execute("SELECT * FROM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 15/02/2013 02:45, Andrew McNamara ha scritto:
>> For my Python DBAPI2 PostgreSQL driver I plan the following optimizations:
>
> I suggest you have a look at my Python ocpgdb driver:
>
> http://code.google.com/p/ocpgdb/
>
Thanks, I did not kn
>For my Python DBAPI2 PostgreSQL driver I plan the following optimizations:
I suggest you have a look at my Python ocpgdb driver:
http://code.google.com/p/ocpgdb/
It uses the v3 binary protocol exclusively (to avoid the usual escaping
security issues). A number of gotchyas were discovered al
On 14/02/2013 20:01, Peter Eisentraut wrote:
On 2/14/13 9:23 AM, Manlio Perillo wrote:
1) always use PQsendQueryParams functions.
This will avoid having to escape parameters, as it is done in
psycopg2
(IMHO it still use simple query protocol for compatibility purpose)
I think the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 14/02/2013 20:01, Peter Eisentraut ha scritto:
> On 2/14/13 9:23 AM, Manlio Perillo wrote:
>> 1) always use PQsendQueryParams functions.
>>
>>This will avoid having to escape parameters, as it is done in
>>psycopg2
>>(IMHO it still use s
On 2/14/13 9:23 AM, Manlio Perillo wrote:
> 1) always use PQsendQueryParams functions.
>
>This will avoid having to escape parameters, as it is done in
>psycopg2
>(IMHO it still use simple query protocol for compatibility purpose)
I think the reason this doesn't work is that in order
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 14/02/2013 18:18, Jonathan Rogers ha scritto:
> A number of the described features sound quite useful. Is it not
> practical to extend an existing library such as psycopg2?
I suspect there are compatibility issues.
> What method
> will you use to
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 14/02/2013 14:06, Albe Laurenz ha scritto:
> Manlio Perillo wrote:
>> Sorry for the question, but where can I find the libpq test suite?
>> I can not find it in the PostgreSQL sources; it seems that there are
>> only some examples, in src/test/examp
11 matches
Mail list logo
