Re: RETURNING syntax for COPY

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Karol Trzcionka <karlikt(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: RETURNING syntax for COPY
Date: 2013-05-08 16:40:54
Message-ID: CAFj8pRAfEBukT+pnzmvVaiBY0HwnX=VqBgPz7WrUmFBn6X5krg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello

why? What is motivation? What is use case?

Regards

Pavel

2013/5/8 Karol Trzcionka <karlikt(at)gmail(dot)com>

> Hello,
> as a continuation of my proposal expanding RETURNING syntax by
> AFTER/BEFORE, there can be enough time to implement RETURNING for COPY.
> I'd like to hear your opinion on that. My draft idea is:
> COPY FROM ... RETURNING table_name.* -> returns all values copied to
> table after all triggers invoke
> COPY FROM ... RETURNING BEFORE.* -> returns all values copied to table
> before triggers (all raw values from file)
> COPY TO ... RETURNING table_name.* -> returns all values from table
> COPY TO ... RETURNING AFTER.*/BEFORE.* -> the same
> What do you think about?
> Regards,
> Karol Trzcionka
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-05-08 16:44:59 Re: RETURNING syntax for COPY
Previous Message Peter Eisentraut 2013-05-08 16:34:29 Re: improving PL/Python builds on OS X