Re: [GENERAL] encoding and LC_COLLATE

2011-11-15 Thread LPlateAndy
Hi Adrian/Mark Thanks again for your help, i have now got the load working by setting the encoding to WIN1252. I had been assuming i was setting it to UTF8 SET CLIENT_ENCODING TO 'WIN1252'; Andy -- View this message in context: http://postgresql.1045698.n5.nabble.com/encoding-and-LC-COLLATE-tp

Re: [GENERAL] encoding and LC_COLLATE

2011-11-15 Thread LPlateAndy
Hi Mark (and Adrian), As as update i've now found the same data fails on my postgres 8 which doesn't seem to have the LC_COLLATE etc setting and is just UTF-8 so i guess there is possibly just something about the way the data is getting passed in. This is the error message from postgres 9

Re: [GENERAL] encoding and LC_COLLATE

2011-11-14 Thread Mark Watson
De : pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] De la part de Adrian Klaver >Envoyé : 14 novembre 2011 13:03 >... > >Second is the data coming in actually UTF8 or some other encoding? >...  Hi Andy, I have to agree with Adrian in that the data may be coming in

Re: [GENERAL] encoding and LC_COLLATE

2011-11-14 Thread Adrian Klaver
On Mon, Nov 14, 2011 at 8:25 AM, LPlateAndy wrote: > Hi Adrian, > > ** ** > > You’re right, i’m trying to get the copy command to put a load of data > into a table. It’s now working fine except for any instances with an e acute > > > ** ** > > I tried putting “ SET CLIENT_ENCODING TO ‘UT

Re: [GENERAL] encoding and LC_COLLATE

2011-11-14 Thread LPlateAndy
Hi Adrian, You're right, i'm trying to get the copy command to put a load of data into a table. It's now working fine except for any instances with an e acute I tried putting " SET CLIENT_ENCODING TO 'UTF-8'; " but still got the error. I guess that just because i'm verifying what's incoming

Re: [GENERAL] encoding and LC_COLLATE

2011-11-14 Thread Adrian Klaver
On Monday, November 14, 2011 3:03:32 am LPlateAndy wrote: > Hi, > > I set up my postgres 9.0 install 6 months ago and generally everything is > fine but a recent data load with an e acute character failed which an > unsupported message which surprised me as we're using UTF-8. > > However, i can

Re: [GENERAL] encoding and LC_COLLATE

2011-11-14 Thread LPlateAndy
Hi, In response to my own question i have now read the following: http://stackoverflow.com/questions/6579621/lc-collate-and-lc-ctype-suport-for-utf-8-in-postgresql It seems to show that apart from a complete reinstall i should just use a Locale of C (as i'm on Windows and POSIX wont work). This

[GENERAL] encoding and LC_COLLATE

2011-11-14 Thread LPlateAndy
Hi, I set up my postgres 9.0 install 6 months ago and generally everything is fine but a recent data load with an e acute character failed which an unsupported message which surprised me as we're using UTF-8. However, i can now see that the listing for the database set up show a restriction unde