| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Brice Ruth <brice(at)webprojkt(dot)com> |
| Cc: | Michael Fork <mfork(at)toledolink(dot)com>, Ian Harding <iharding(at)pakrat(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: [SQL] Re: SQL Join - MySQL/PostgreSQL difference? |
| Date: | 2001-02-07 16:14:32 |
| Message-ID: | 28516.981562472@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
Brice Ruth <brice(at)webprojkt(dot)com> writes:
> Here's my latest tactic: I'm guessing that the data 'corruption' has
> something to do with the way the data was exported from the original
> database by the third party ... probably something with the cr/lf
> linebreaks or something to that effect (the data field in question
> happens to be the last field in a line in the data file).
Ooooh ... the queries you were showing us made it look like the column
was not the last one, so I hadn't thought of that. Almost certainly,
your extra character is a CR. Postgres expects plain LF as newline in
COPY data files; if the newlines are actually CR/LF then the CRs will
be taken as part of the last data field.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Alliban | 2001-02-07 16:20:10 | Re: Number of open files |
| Previous Message | Brice Ruth | 2001-02-07 16:07:55 | Re: [SQL] Re: SQL Join - MySQL/PostgreSQL difference? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brice Ruth | 2001-02-07 16:38:53 | Re: [SQL] Re: SQL Join - MySQL/PostgreSQL difference? |
| Previous Message | Brice Ruth | 2001-02-07 16:07:55 | Re: [SQL] Re: SQL Join - MySQL/PostgreSQL difference? |