RETURNING syntax for COPY - Mailing list pgsql-hackers

From Karol Trzcionka
Subject RETURNING syntax for COPY
Date
Msg-id 518A742E.9020909@gmail.com
Whole thread Raw
Responses Re: RETURNING syntax for COPY  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: RETURNING syntax for COPY  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: RETURNING syntax for COPY  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Fix permission tests for views/tables proven empty by constraint
Next
From: Dave Page
Date:
Subject: Re: improving PL/Python builds on OS X