From: | "W(dot) Matthew Wilson" <matt(at)tplus1(dot)com> |
---|---|
To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to insert either a value or the column default? |
Date: | 2014-08-25 13:32:11 |
Message-ID: | CAGHfCUDme7mQixru2_gRbif6kcLLaf3SQBQMTitPHmcsrLa4xw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Aug 24, 2014 at 2:50 PM, Daniele Varrazzo
<daniele(dot)varrazzo(at)gmail(dot)com> 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?
Thanks again!
From | Date | Subject | |
---|---|---|---|
Next Message | Sameer Thakur | 2014-08-25 13:40:05 | Re: Using fmgr_hook |
Previous Message | Marc Mamin | 2014-08-25 13:03:56 | Re: Way to identify the current session's temp tables within pg_class ? |