From: | Michael Nolan <htfoot(at)gmail(dot)com> |
---|---|
To: | Ravi Krishna <ravikrishna(at)mail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Guntry Vinod <GV00619735(at)techmahindra(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Venkatamurali Krishna Gottuparthi <VG00114307(at)techmahindra(dot)com>, Biswa Ranjan Dash <BD00617837(at)techmahindra(dot)com> |
Subject: | Re: Back Slash \ issue |
Date: | 2019-05-03 14:43:32 |
Message-ID: | CAOzAqu+tQ5v4pHDw=M7=+ZQ3k+600yY-nnMFPDpZk_hQcTkSiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, May 3, 2019 at 9:35 AM Ravi Krishna <ravikrishna(at)mail(dot)com> wrote:
> >
> > In what format are you dumping the DB2 data and with what specifications
> e.g. quoting?
> >
>
> DB2's export command quotes the data with "". So while loading, shouldn't
> that take care of delimiter-in-the-data issue ?
>
I don't think we've seen enough representative data to know exactly what
the backslash is doing. It doesn't appear to be an escape, based on the
sole example I've seen it appears to be a data separator between first name
and last name.
It seems increasingly likely to me that you might not be in a position
where the COPY command in PostgreSQL can handle loading the database, at
least not without some help. You might have to write a program to clean up
the data and format it for PostgreSQL.
I've spent a lot of time over the years migrating data from one platform to
another, you have to know EXACTLY what data you currently have and what
format you need it turned into before you can figure out how to do the
transformation.
--
Mike Nolan
From | Date | Subject | |
---|---|---|---|
Next Message | Ravi Krishna | 2019-05-03 15:13:06 | Re: Back Slash \ issue |
Previous Message | Adrian Klaver | 2019-05-03 14:39:10 | Re: Back Slash \ issue |