From: | "Bertin, Philippe" <philippe(dot)bertin(at)barco(dot)com> |
---|---|
To: | joe(at)jwebmedia(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Using COPY |
Date: | 2002-05-14 14:26:35 |
Message-ID: | B9E404D03707D511BD4D00105A40C10466B6CC@wevmex01.barco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi, Joe,
I'd say : make an ODBC- connection to the PostgreSQL database from within
Access. Then, import the (local) Access table's data into the linked Access
table. I think this should do (provided you don't have some other exotic
conversion needs). I wouldn't convert the Access data into text format and
import these into PostgreSQL?
Regards,
Philippe Bertin.
> -----Original Message-----
> From: Joseph Koenig [SMTP:joe(at)jwebmedia(dot)com]
> Sent: dinsdag 14 mei 2002 16:15
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] Using COPY
>
> We're converting a db from Access to PostgreSQL for a client - I need to
> export all of his data into postgres on Linux - I'm trying to use the
> COPY command, however, his comment fields have line breaks in them which
> causes the copy to throw a parse error at that line. I'm sure others
> have run into this - is there an easy way to avoid this? Thanks,
>
> Joe
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | tony | 2002-05-14 14:30:13 | Re: Using COPY |
Previous Message | Erwin Ambrosch | 2002-05-14 14:24:13 | Question about SERIAL |