Re: [GENERAL] Hex characters in COPY input

2015-02-27 Thread Melvin Call
On Fri, Feb 27, 2015 at 12:02 PM, Adam Hooper wrote: > On Fri, Feb 27, 2015 at 9:39 AM, Melvin Call wrote: >> On 2/26/15, Vick Khera wrote: >>> On Thu, Feb 26, 2015 at 9:50 PM, Melvin Call >>> wrote: >>> I get an error "ERROR: invalid byte sequence for encoding "UTF8": 0xe9616c" >>>

Re: [GENERAL] Hex characters in COPY input

2015-02-27 Thread Adam Hooper
On Fri, Feb 27, 2015 at 9:39 AM, Melvin Call wrote: > On 2/26/15, Vick Khera wrote: >> On Thu, Feb 26, 2015 at 9:50 PM, Melvin Call >> wrote: >> >>> I get an error "ERROR: invalid byte sequence for >>> encoding "UTF8": 0xe9616c" >> >> Character code E9 is not UTF8. Don't tell Postgres you're im

Re: [GENERAL] Hex characters in COPY input

2015-02-27 Thread Adrian Klaver
On 02/27/2015 07:55 AM, Melvin Call wrote: On Fri, Feb 27, 2015 at 9:03 AM, Adrian Klaver wrote: On 02/27/2015 06:39 AM, Melvin Call wrote: On 2/26/15, Vick Khera wrote: On Thu, Feb 26, 2015 at 9:50 PM, Melvin Call wrote: Montreal where the e is an accented e. The output ends up in the

Re: [GENERAL] Hex characters in COPY input

2015-02-27 Thread Melvin Call
On Fri, Feb 27, 2015 at 9:03 AM, Adrian Klaver wrote: > On 02/27/2015 06:39 AM, Melvin Call wrote: >> >> On 2/26/15, Vick Khera wrote: >>> >>> On Thu, Feb 26, 2015 at 9:50 PM, Melvin Call >>> wrote: >>> Montreal where the e is an accented e. The output ends up in the text file as

Re: [GENERAL] Hex characters in COPY input

2015-02-27 Thread Melvin Call
On Fri, Feb 27, 2015 at 8:58 AM, Adam Hooper wrote: > On Fri, Feb 27, 2015 at 9:39 AM, Melvin Call wrote: >> On 2/26/15, Vick Khera wrote: > >>> Character code E9 is not UTF8. Don't tell Postgres you're importing UTF8 if >>> you're not. >>> >> Thank you Vic, adding the ENCODING 'latin1' option t

Re: [GENERAL] Hex characters in COPY input

2015-02-27 Thread Adrian Klaver
On 02/27/2015 06:39 AM, Melvin Call wrote: On 2/26/15, Vick Khera wrote: On Thu, Feb 26, 2015 at 9:50 PM, Melvin Call wrote: Montreal where the e is an accented e. The output ends up in the text file as Montr\xe9al, where the xe9 is a single character. When I try to copy that into my Postgre

Re: [GENERAL] Hex characters in COPY input

2015-02-27 Thread Melvin Call
On 2/27/15, Adam Hooper wrote: > On Thu, Feb 26, 2015 at 9:50 PM, Melvin Call > wrote: > >> So my question is, how do I sanitize the hex character in the middle of a >> word >> to be able to copy in Montreal with an accented e? Or am I going about >> this at >> the wrong point? > > Hi Melvin, > >

Re: [GENERAL] Hex characters in COPY input

2015-02-27 Thread Melvin Call
On 2/26/15, Vick Khera wrote: > On Thu, Feb 26, 2015 at 9:50 PM, Melvin Call > wrote: > >> Montreal where the e is an accented e. The output ends up in the text >> file >> as >> Montr\xe9al, where the xe9 is a single character. When I try to copy that >> into >> my PostgreSQL table, I get an erro

Re: [GENERAL] Hex characters in COPY input

2015-02-26 Thread Vick Khera
On Thu, Feb 26, 2015 at 9:50 PM, Melvin Call wrote: > Montreal where the e is an accented e. The output ends up in the text file > as > Montr\xe9al, where the xe9 is a single character. When I try to copy that > into > my PostgreSQL table, I get an error "ERROR: invalid byte sequence for > encod