Re: RETURNING syntax for COPY
| От | Pavel Stehule |
|---|---|
| Тема | Re: RETURNING syntax for COPY |
| Дата | |
| Msg-id | CAFj8pRAfEBukT+pnzmvVaiBY0HwnX=VqBgPz7WrUmFBn6X5krg@mail.gmail.com обсуждение исходный текст |
| Ответ на | RETURNING syntax for COPY (Karol Trzcionka <karlikt@gmail.com>) |
| Список | pgsql-hackers |
Hello
why? What is motivation? What is use case?2013/5/8 Karol Trzcionka <karlikt@gmail.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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: