Bill Studenmund wrote:
>>
>>But as long as COPY IN considers that delimiter spec to mean "any one of
>>these characters", and not a multicharacter string, we couldn't do that.
>>
>>If we restrict DELIMITERS strings to be exactly one character for a
>>release or three, we could think about implementing this idea of
>>multicharacter delimiter strings later on. Not sure if anyone really
>>needs it though.
>>
\r\n is quite popular (row) delimiter on some systems (and causes
sometimes a weird box
char to appear at the end of last database field :), but I doubt I can
give any examples
of multichar field delimiters
>> In any case, the current behavior is inconsistent.
>>
>
>I think this restriction sounds fine, and quite practical. :-)
>
I sincerely doubt that anyone knowingly :) uses this undocumented
feature for copy in,
as it can be found out only by trial and error.
Much better to remove it, enforce it in code as Bruce suggested, and
document it.
------------------
Hannu
