From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | "W(dot) Matthew Wilson" <matt(at)tplus1(dot)com>, 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 14:26:48 |
Message-ID: | 53FB47A8.5080100@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/25/2014 06:32 AM, W. Matthew Wilson wrote:
> 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?
Here is the email laying out the issues:
http://www.postgresql.org/message-id/AANLkTi=ym3SCQKCQBtp8RJHUswwAPOpjXYKTXS=aHWzp@mail.gmail.com
>
> Thanks again!
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Daniele Varrazzo | 2014-08-25 15:36:00 | Re: How to insert either a value or the column default? |
Previous Message | Emanuel Calvo | 2014-08-25 14:20:45 | Re: Constraint exclusion on tables partitioned over range types |