On Mon, Nov 14, 2011 at 8:25 AM, LPlateAndy <a...@centremaps.co.uk> 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 ‘UTF-8’; ” but still got the > error. I guess that just because i’m verifying what’s incoming, it doesn’t > mean it’s going to go into a database which doesn’t support it?**** > > ** ** > > Let me know if i’m missing something! > First what is the actual error message you are getting? Second is the data coming in actually UTF8 or some other encoding? > **** > > ** ** > > Cheers**** > > ** ** > > Andy**** > > ** ** > > ** ** > > *From:* Adrian Klaver-3 [via PostgreSQL] [mailto:[hidden > email]<http://user/SendEmail.jtp?type=node&node=4991287&i=0>] > > *Sent:* 14 November 2011 15:15 > *To:* LPlateAndy > *Subject:* Re: encoding and LC_COLLATE**** > > ** ** > > 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 now see that the listing for the database set up show a > > restriction under LC_COLLATE and LC_CTYPE to the UK which would explain > the > > blocking of this character. Oddly, this is set even if i only specify > UTF-8 > > which i guess means that it is set against the template. I can only > assume > > that i selected this option on install but have since forgotten. > > > > CREATE DATABASE testing > > WITH OWNER = postgres > > ENCODING = 'UTF8' > > TABLESPACE = pg_default > > LC_COLLATE = 'English_United Kingdom.1252' > > LC_CTYPE = 'English_United Kingdom.1252' > > CONNECTION LIMIT = -1; > > > > Is there any way that i can change this, preferably against the > template. > > > > If i try creating a new database by right clicking at the top of the > > database tree in pgAdmin i do note that i also have the options of "C" > or > > "POSIX" but have read elsewhere that these are even more restrictive. > > > > Any ideas - hoping to avoid a complete re-install! **** > > See: > click here. > See how NAML generates this > email<http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.InstantMailNamespace&breadcrumbs=instant+emails%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > **** > ------------------------------ > View this message in context: RE: encoding and > LC_COLLATE<http://postgresql.1045698.n5.nabble.com/encoding-and-LC-COLLATE-tp4990415p4991287.html> > > Sent from the PostgreSQL - general mailing list > archive<http://postgresql.1045698.n5.nabble.com/PostgreSQL-general-f1843780.html>at > Nabble.com. > -- Adrian Klaver adrian.kla...@gmail.com
