Am 27.09.2012 09:47, schrieb Federico Di Gregorio:
> On 27/09/2012 09:35, Tobias Oberstein wrote:
>> My use case is this: all DB access is via Stored Procedures (SP) on a
>> pool of long lived DB connections. The set of eligible SPs is determined
>> in advance. Hence, something that does not lead to reparsing/replanning
>> of the SP call SELECT statements on every execution is desirable.
>> I notice there is
>> Does Psycopg support this?
Then I am definitely interested in helping bringing support for prepared
stuff and also fastpath-SP-calls to Pscyopg (since the API for both seem
to be somewhat similar).
In response to
psycopg by date
|Next:||From: Daniele Varrazzo||Date: 2012-09-28 01:32:42|
|Subject: Prepared statements [was: Session state per transaction]|
|Previous:||From: Federico Di Gregorio||Date: 2012-09-27 07:47:58|
|Subject: Re: Session state per transaction|