| From: | Ravi Krishna <ravikrishna(at)mail(dot)com> |
|---|---|
| To: | Michael Nolan <htfoot(at)gmail(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 15:13:06 |
| Message-ID: | 346D2F54-D13D-4C45-9E42-1E51F36ED85F@mail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> 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
Fully agreed. I have informed Guntry via email that he has to provide more information before we can help further.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rihad | 2019-05-03 15:41:15 | Re: Upgrading locale issues |
| Previous Message | Michael Nolan | 2019-05-03 14:43:32 | Re: Back Slash \ issue |