Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> Which we do not have, because pg_dump doesn't use CSV. I do not think > >> this is a must-fix, especially not if the proposed fix introduces > >> inconsistencies elsewhere. > > > Sure, pg_dump doesn't use it but COPY should be able to load anything it > > output. > > I'd buy into that proposition if CSV showed any evidence of being a > sanely defined format, but it shows every indication of being neither > well-defined, nor self-consistent, nor even particularly portable. > I suggest adjusting your expectations. All I expect from that code is > being able to load the majority of data from the more popular Microsloth > applications. Trying to achieve 100% consistency for corner cases is > just going to interfere with the real use-case for the feature, which is > coping with output from applications that aren't very consistent in the > first place.
OK, then should we disallow dumping out data in CVS format that we can't load? Seems like the least we should do for 8.0. -- 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 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
