On 08/25/2014 06:32 AM, W. Matthew Wilson wrote:
On Sun, Aug 24, 2014 at 2:50 PM, Daniele Varrazzo
<daniele.varrazzo@xxxxxxxxx> wrote:
It should be added to the library (it was first discussed in 2003...),
but it's one of these things that will stop working when psycopg will
start using the "extended query protocol" (together with other nifty
features such as string literals for table/columns names) so in my
mind it can only be included when psycopg will be able to do both
client-side parameter interpolation and server-side arguments passing,
and when the distinction between the two strategies will be clear
(this is planned for a future psycopg3 but there is no timeline for it
yet).
First of all, thanks for showing this trick!
But I am confused. Will this trick stop working in a future version
of psycopg2? Should I avoid using it?
Here is the email laying out the issues:
http://www.postgresql.org/message-id/AANLkTi=ym3SCQKCQBtp8RJHUswwAPOpjXYKTXS=aHWzp@xxxxxxxxxxxxxx
Thanks again!
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
