On Sun, 2003-10-05 at 22:38, Tom Lane wrote:
> Modify COPY FROM to match the null-value string against the column value
> before it is de-backslashed, not after. This allows the null string \N
> to be reliably distinguished from the data value \N (which must be
> represented as \\N). Per bug report from Manfred Koizar ... but it's
> amazing this hasn't been reported before ...
> Also, be consistent about encoding conversion for null string: the form
> specified in the command is in the server encoding, but what is sent
> to/from client must be in client encoding. This never worked quite
> right before either.
Should either of these be backpatched to 7.3?
-Neil
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
