From: | "Jens P(dot) Elsner" <jpelsner(at)gmx(dot)net> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Migrating from Sybase |
Date: | 2000-07-24 22:32:37 |
Message-ID: | 20000725003236.A2444@ice.anydomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Had a similar experience in Postgresql 6.5.3 running in Linux with *.dat files
> coming from Sybase running in win95.
>
> Found that if I split the source file with a text editor that the individual
> splits would process ok. Finally concluded that Sybase was putting a
> character at end of file that 'COPY' could not interpret.
At the end of each line, the <cr>. recode fixed it.
> Also, had trouble with null fields. I had Sybase generate a unique date for
> nulls and 0 for null integers. But then, my 'copy' command didn't include
> 'with null as ''.
Ok.
> Further, changed all char fields to varchar because postgres stumbled on
> character lengths that didn't match char(length).
No problem with that.
> Hope this helps.
Yup, thanks a lot!
JP
From | Date | Subject | |
---|---|---|---|
Next Message | Jens P. Elsner | 2000-07-24 22:33:41 | Re: Migrating from Sybase |
Previous Message | Jesus Aneiros | 2000-07-24 22:25:03 | RULES on PostgreSQL |