Re: Back Slash \ issue - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Back Slash \ issue
Date
Msg-id 856f0d11-c59a-c1c6-dd4d-a90bfad14131@aklaver.com
Whole thread Raw
In response to RE: Back Slash \ issue  (Guntry Vinod <GV00619735@TechMahindra.com>)
Responses RE: Back Slash \ issue
List pgsql-general
On 5/3/19 9:05 AM, Guntry Vinod wrote:
> Hi Team,
> 
> Here we go. I will give the problem in more detail
> 
> Step 1:We get the dump from DB2 and this dump is flat file which can be csv,txt
> Step2:There is table in PostGre where we are suppose  to upload the dump
> Step3:We are using copy command to upload dump to the table using (COPY <<TableName>> from 'C:\Data_Dump\ABC.txt'
DELIMITER'|';  )
 

Should have been in my previous post. The answer to whether Step 1 is 
text or CSV is important as that determines the way you use the COPY 
command above. As has been pointed out upstream using COPY assuming 
text(as you are doing above) on a CSV file will create issues.

> Step 4:In the above step we are using delimiter because the data is separated (:) in the flat which we have received
fromthe flat file
 
> 
> Problem Statement:We are able to upload the data from the flat file which we got from the DB2 but few data the data
consistof  " \".For example if the CustomerName is Vinod\G in the flat file ,we expect the same data in PostGre  table
forCustomerName as Vinod\G but we see VinodG(slash is missed).
 
> 
> Possible Solution: We can replace "\" with "\\" but if the file is in too large we cannot open it(we can replace if
thefile is medium or small)
 
> 
> Expectation: We need a command or utility which can upload the data as it is (for example if Vinod\G then we should
seein PostGre as Vinod\G but not VinodG)
 
> 
> Hope Iam detail this time :-)
> 
> Regards,
> Vinod
> 
> 
>   
> 



-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Back Slash \ issue
Next
From: Michael Nolan
Date:
Subject: Re: Back Slash \ issue