Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
| От | Dave Cramer |
|---|---|
| Тема | Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work |
| Дата | |
| Msg-id | A89C6CD8-333A-4BE9-AC22-5F1181B95886@fastcrypt.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-jdbc |
So if I write
conn.prepareStatement("select col from table where col like ?")
then setString(1,'hello%')
The driver will do
prepare foo as select col from table where col like $1
and then
execute foo('hello%')
this will take advantage of the strategy automatically ?
If so this should be changed. The driver does this all the time.
Dave
On 1-Apr-08, at 10:06 AM, Tom Lane wrote:
> Dave Cramer <pg@fastcrypt.com> writes:
>> Was the driver ever changed to take advantage of the above strategy?
>
> Well, it's automatic as long as you use the unnamed statement. About
> all that might need to be done on the client side is to use unnamed
> statements more often in preference to named ones, and I believe that
> something like that did get done in JDBC.
>
> regards, tom lane
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-jdbc по дате отправления: