On Thu, 18 Feb 2010 16:09:42 +0100, Dimitri Fontaine
> "Pierre C" <lists(at)peufeu(dot)com> writes:
>> Problem with prepared statements is they're a chore to use in web apps,
>> especially PHP, since after grabbing a connection from the pool, you
>> know if it has prepared plans in it or not.
> Have you met preprepare yet?
Hey, this thing is nice.
How hard would it be to put a hook in pg so that, instead of raising an
error and cancelling the txn when EXECUTing a statement that is not
prepared, it would call a user function (of the user's choice) which
would, if possible, prepare said statement, or if not, raise the error ?
In response to
pgsql-hackers by date
|Next:||From: Dimitri Fontaine||Date: 2010-02-18 16:54:31|
|Subject: Re: Avoiding bad prepared-statement plans.|
|Previous:||From: Dimitri Fontaine||Date: 2010-02-18 15:52:48|
|Subject: Re: remove contrib/xml2|