Re: unicode troubles and postgres

2014-01-10 Thread wxjmfauth
Le jeudi 9 janvier 2014 19:49:27 UTC+1, Ethan Furman a écrit : > So I'm working with postgres, and I get a datadump which I try to restore to > my test system, and I get this: > > > > ERROR: value too long for type character varying(4) > > CONTEXT: COPY res_currency, line 32, column symbol:

Re: unicode troubles and postgres [SOLVED]

2014-01-09 Thread Chris Angelico
On Fri, Jan 10, 2014 at 6:51 AM, Ethan Furman wrote: > The problem was I had created the database from template0 instead of > template1, and 0 is SQL-ASCII while 1 is UTF8. Ah, this is one of the traps with Postgres. This is one of the reasons I prefer not to touch template[01] and to script the

Re: unicode troubles and postgres [SOLVED]

2014-01-09 Thread Ethan Furman
On 01/09/2014 10:49 AM, Ethan Furman wrote: So I'm working with postgres, and I get a datadump which I try to restore to my test system, and I get this: ERROR: value too long for type character varying(4) CONTEXT: COPY res_currency, line 32, column symbol: "руб" "py6" sure looks like it shou

Re: unicode troubles and postgres

2014-01-09 Thread Peter Otten
Ethan Furman wrote: > So I'm working with postgres, and I get a datadump which I try to restore > to my test system, and I get this: > > ERROR: value too long for type character varying(4) > CONTEXT: COPY res_currency, line 32, column symbol: "руб" > > "py6" sure looks like it should fit, but