Bruce Momjian wrote:
Tom Lane wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Tom Lane wrote:I'd buy into that proposition if CSV showed any evidence of being a
Which we do not have, because pg_dump doesn't use CSV. I do not thinkSure, pg_dump doesn't use it but COPY should be able to load anything it
this is a must-fix, especially not if the proposed fix introduces
inconsistencies elsewhere.
output.
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.
As Tom rightly points out, having data make the round trip was not the goal of the exercise. Excel, for example, has no trouble reading such data (or at least my installation of it).
Personally I consider CSVs with line end chars embedded in fields to be broken anyway, but this was something that was specifically mentioned when we were discussing requirements, which is why I coded for it.
cheers
andrew
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
