Re: ecpg command does not warn COPY ... FROM STDIN;
От | Tom Lane |
---|---|
Тема | Re: ecpg command does not warn COPY ... FROM STDIN; |
Дата | |
Msg-id | 1655950.1736350929@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: ecpg command does not warn COPY ... FROM STDIN; (Fujii Masao <masao.fujii@oss.nttdata.com>) |
Ответы |
Re: ecpg command does not warn COPY ... FROM STDIN;
|
Список | pgsql-hackers |
Fujii Masao <masao.fujii@oss.nttdata.com> writes: > On 2025/01/08 23:04, Ryo Kanbayashi wrote: > But it is not working. > ecpg command fails to notice though code like above exits on pgc code. > This issue seems to have been introduced in commit 3d009e45bd. Indeed :-( > As for COPY FROM STDOUT, while it's possible, mentioning it might be > confusing since it's not official syntax. So I'm not sure if this is > good idea. There's another problem: the correct syntax is COPY TO STDOUT, and that won't trigger this warning either. I'm inclined to drop the test on @5 altogether, and just check for "stdin" or "stdout" in @7. There is no variant of those that will work. (But maybe we should allow it if opt_program isn't empty?) The warning message could perhaps be written "COPY FROM STDIN/TO STDOUT is not implemented". regards, tom lane
В списке pgsql-hackers по дате отправления: