Thanks for your response Robert.
Unfortunately I don't think that will work (unless I'm misunderstanding
something).
I can't export using a client encoding of WIN1250 because I have true
UNICODE chars which can't be represented with it (I've tried and I get
the error below). Therefore, I
Meetesh Karia [EMAIL PROTECTED] writes:
Additionally, here's what I get when I run your test below (my server
encoding is UTF-8):
ltefull=# create table x (r varchar(255) unique);
NOTICE: CREATE TABLE / UNIQUE will create implicit index x_r_key for
table x
CREATE TABLE
ltefull=#
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 like this for the regression tests. The only
one I was aware of previously was the Turkish one.
--
Gregory Stark
EnterpriseDB
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 like
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
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 the
command I was running was:
create unique index foo_name on foo (name);
If I use the following, it now works:
create unique index
