On Tue, Nov 1, 2016 at 12:40 PM, Haribabu Kommi <kommi.harib...@gmail.com> wrote: > COPY command is treated as an UTILITY command, During the query > processing, the rules are not applied on the COPY command, and in the > execution of COPY command, it just inserts the data into the heap and > indexes with direct calls. > > I feel supporting the COPY command for the case-2 is little bit complex > and may not be that much worth.
I agree it will be complex.. > > Attached is the updated patch with doc changes. Now since we are adding support for INSTEAD OF TRIGGER in COPY FROM command, It will be good that we provide a HINT to user if INSTEAD of trigger does not exist, like we do in case of insert ? INSERT case: postgres=# insert into ttt_v values(7); 2016-11-01 14:31:39.845 IST [72343] ERROR: cannot insert into view "ttt_v" 2016-11-01 14:31:39.845 IST [72343] DETAIL: Views that do not select from a single table or view are not automatically updatable. 2016-11-01 14:31:39.845 IST [72343] HINT: To enable inserting into the view, provide an INSTEAD OF INSERT trigger or an unconditional ON INSERT DO INSTEAD rule. COPY case: postgres=# COPY ttt_v FROM stdin; 2016-11-01 14:31:52.235 IST [72343] ERROR: cannot copy to view "ttt_v" 2016-11-01 14:31:52.235 IST [72343] STATEMENT: COPY ttt_v FROM stdin; -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
