Andrew Dunstan wrote: > In fact, in the patch I sent in, no quoted string is marked as null when > being read (so even if you use \N as the null marker, "\N" will be that > literal and not a null marker). And the null marker, whatever it is, > should be made quote safe by us throwing an error if it contains the > quote marker, just as we now make sure that the null marker is > delimiter-safe.
What value does an int column get if the input file has ',,'. Don't tell me zero? :-) Error? > I will check on the write behaviour - it might need ammending too. > > I'll submit a revised patch based on the original syntax scheme, and > then you (Bruce) can make the syntax/psql changes that seem to be agreed > on now - is that ok? OK, go as far as you want and post it. I will turn around a new patch in a few hours after you post. > The default NULL value issue can be determined at the end of any > exhaustive debate we have - in the end it's a one line code change ;-) Agreed. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
