Re: [RFC] ideas for a new Python DBAPI driver (was Re: libpq test suite)

Поиск
Список
Период
Сортировка
От Marko Tiikkaja
Тема Re: [RFC] ideas for a new Python DBAPI driver (was Re: libpq test suite)
Дата
Msg-id 511D3E30.1020102@joh.to
обсуждение исходный текст
Ответ на Re: [RFC] ideas for a new Python DBAPI driver (was Re: libpq test suite)  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: [RFC] ideas for a new Python DBAPI driver (was Re: libpq test suite)  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers
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 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 tbl WHERE a = %s AND b = %s", (val1, val2))
>
> what types will you pass to PQsendQueryParams?

Pardon me if this is obvious, but why would you need to pass any types 
at all?  Assuming we're still talking about PQsendQueryParams and not an 
explicit prepare/execute cycle..


Regards,
Marko Tiikkaja



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Manlio Perillo
Дата:
Сообщение: Re: [RFC] ideas for a new Python DBAPI driver (was Re: libpq test suite)
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system