Re: UTF-8 and LIKE vs =

From: David Wheeler <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ian Barwick <barwick(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: UTF-8 and LIKE vs =
Date: 2004-08-23 23:18:00
Message-ID: AD29016C-F55A-11D8-990D-000A95972D84@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Aug 23, 2004, at 4:08 PM, Tom Lane wrote:

> [ looks back at discussion... ] Actually I misremembered --- the
> discussion was about how we would *reject* legal UTF-8 codes that are
> more than 2 bytes long. So the code is broken, but not in the
> direction
> that would cause your problem. Time for another theory.

Whew!

> Is the problem query using an index? If so, does REINDEX help?

Doesn't look like it:

bric=# reindex index udx_keyword__name;
REINDEX
bric=# select * from keyword where name ='북한의';
id | name | screen_name | sort_name | active
------+--------+-------------+-----------+--------
1218 | 국방비 | 국방비 | 국방비 | 1
(1 row)

That's still giving me an invalid row for the value I passed to it
(note that the value of the "name" column is different than the value I
queried for).

Regards,

David

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Josué Maldonado 2004-08-23 23:30:11 Re: pg_dump/psql fails on win32 beta 8.0
Previous Message Josué Maldonado 2004-08-23 23:13:35 pg_dump/psql fails on win32 beta 8.0