Postgres Pro
Downloads
Home   >   mailing lists

Re: encoding confusion with \copy command - Mailing list pgsql-general

From Martin Waite
Subject Re: encoding confusion with \copy command
Date
Msg-id CAOWKics9=Roo+yxoue1NnMNBW3FFp7qcZ6XYKuXf84__evPP3Q@mail.gmail.com
Whole thread Raw
In response to Re: encoding confusion with \copy command  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: encoding confusion with \copy command
List pgsql-general
Tree view
You are right that I need an intermediate step.  I will probably use a CSV parser that is liberal in what it accepts, but writes out strict CSV data suitable for postgres.

Thanks for the help.

On 17 September 2014 15:40, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 09/17/2014 06:48 AM, Martin Waite wrote:
Hi Adrian,

I apologise - I meant 9.4

 Looks like you will need an intermediate step. A quick search found the below which might offer a solution:

http://www.excel-sql-server.com/sql-server-export-to-excel-using-bcp-sqlcmd-csv.htm

FYI the good stuff is at the bottom.

There is also this SO answer that refers to SQL Server Management Studio(not sure if you have):

http://stackoverflow.com/questions/6115054/how-to-get-export-output-in-real-csv-format-in-sql-server-managment-studio



regards,
Martin


--
Adrian Klaver
adrian.klaver@aklaver.com

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: strange problem with not existing roles
Next
From: cowwoc
Date:
Subject: Re: Feature request: temporary schemas