Re: [ADMIN] Encoding problems with migration from 8.0.14 to 8.3.0 on Windows

2008-03-13 Thread Meetesh Karia
Thanks for the confirmation of this. For now I'll continue to use the C locale and I'll switch with 8.3.1. Meetesh Gregory Stark wrote: "Tom Lane" <[EMAIL PROTECTED]> writes: I think this is a "must fix" bug for 8.3.1, anyone disagree? Agreed. It seems we should collect cases lik

Re: [ADMIN] Encoding problems with migration from 8.0.14 to 8.3.0 on Windows

2008-03-13 Thread Meetesh Karia
e C locale, but I'm a bit surprised that the default windows locale wouldn't work. Is that to be expected? Thanks, Meetesh Meetesh Karia wrote: Thanks for your response Robert. Unfortunately I don't think that will work (unless I'm misunderstanding something). I can't e

Re: [ADMIN] Encoding problems with migration from 8.0.14 to 8.3.0 on Windows

2008-03-13 Thread Meetesh Karia
lues ('Daniel Bruehl'); ERROR: duplicate key value violates unique constraint "x_r_key" Meetesh Robert Treat wrote: On Wednesday 12 March 2008 09:37, Meetesh Karia wrote: One quick addition to this: The column I'm creating this unique index on is a varchar(255) and

Re: [ADMIN] Encoding problems with migration from 8.0.14 to 8.3.0 on Windows

2008-03-12 Thread Meetesh Karia
etesh Meetesh Karia wrote: Hi all, I'm trying to migrate from 8.0.14 on Windows (Vista Home Premium) to 8.3.0 and I've been trying to solve what appears to be an encoding problem. My old db was in the UNICODE encoding. I know that this isn't supported on 8.0.x, but it was a re

[ADMIN] Encoding problems with migration from 8.0.14 to 8.3.0 on Windows

2008-03-12 Thread Meetesh Karia
Hi all, I'm trying to migrate from 8.0.14 on Windows (Vista Home Premium) to 8.3.0 and I've been trying to solve what appears to be an encoding problem. My old db was in the UNICODE encoding. I know that this isn't supported on 8.0.x, but it was a restore of a db from a Linux environment an