of
broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Patrick B. Kelly
--
v: 484.557.0646 http://patrickbkelly.org
warehousing.
Patrick B. Kelly
--
http://patrickbkelly.org
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Nov 12, 2004, at 12:20 AM, Tom Lane wrote:
Patrick B Kelly [EMAIL PROTECTED] writes:
I may not be explaining myself well or I may fundamentally
misunderstand how copy works.
Well, you're definitely ignoring the character-set-conversion issue.
I was not trying to ignore the character set
.
Actually, when I try to export a sheet with multi-line cells from
excel, it tells me that this feature is incompatible with the CSV
format and will not include them in the CSV file.
Patrick B. Kelly
--
http
On Nov 11, 2004, at 2:56 PM, Andrew Dunstan wrote:
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Patrick B Kelly wrote:
Actually, when I try to export a sheet with multi-line cells from
excel, it tells me that this feature is incompatible with the CSV
format and will not include them
On Nov 11, 2004, at 6:16 PM, Tom Lane wrote:
Patrick B Kelly [EMAIL PROTECTED] writes:
What about just coding a FSM into
backend/commands/copy.c:CopyReadLine() that does not process any
flavor
of NL characters when it is inside of a data field?
CopyReadLine has no business tracking that. One
On Nov 11, 2004, at 10:07 PM, Andrew Dunstan wrote:
Patrick B Kelly wrote:
My suggestion is to simply have CopyReadLine recognize these two
states (in-field and out-of-field) and execute the current logic only
while in the second state. It would not be too hard but as you
mentioned it is non