Re: encoding confusion with \copy command

On Sep 17, 2014, at 11:52 AM, Martin Waite <waite.134@gmail.com> wrote:

> You are right that I need an intermediate step.  I will probably use a CSV parser that is liberal in what it accepts,
butwrites out strict CSV data suitable for postgres. 
>

If you find such a utility, please share. My clients love Excel, but it takes perfectly valid CSV files and makes them
unreadableby Postgres. In particular, Excel saves rows with fewer columns than the header header row if the cells are
empty.It also mangles valid UTF-8. I often take Excel CSV files and re-save them from Open Office to fix them for
Postgresimport. 

John DeSoi, Ph.D.