Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO
От | Richard Guo |
---|---|
Тема | Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO |
Дата | |
Msg-id | CAMbWs4-szteszfsO=PBSb2cizZqO6D1Gr7f-18-aD0c=LS1m6g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO
|
Список | pgsql-hackers |
On Wed, Jul 27, 2022 at 12:55 PM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote:
ProcessCopyOptions previously rejects force_quote_all for COPY FROM
and copyfrom.c is not even conscious of the option (that is, even no
assertion on it). The two options are rejected for COPY TO by the same
function so it seems like a thinko of the commit. Getting rid of the
code would be good in the view of code coverage and maintenance.
force_null whether it is using COPY FROM and whether it is in CSV mode.
So the codes in copyto.c processing force_notnull/force_null are
actually dead codes.
On the otherhand I wonder if it is good that we have assertions on the
option values.
Agree. Assertions would be better.
Thanks
Richard
Thanks
Richard
В списке pgsql-hackers по дате отправления: