| From: | Adam Berlin <berlin(dot)ab(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
| Subject: | Re: COPY FROM WHEN condition |
| Date: | 2018-11-09 15:51:23 |
| Message-ID: | 154177868369.24563.8425283889569429535.pgcf@coridan.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
As a newcomer to this patch, when I read this example:
COPY table_name WHEN (some_condition)
.. I expect COPY to only be run when the condition is true, and I do not expect the WHEN clause to filter rows. I'm curious what you think about:
COPY table_name WHERE (some_condition)
Users should already be familiar with the idea that WHERE performs a filter.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-11-09 15:59:43 | Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation |
| Previous Message | Nikita Glukhov | 2018-11-09 15:50:05 | Re: jsonpath |