Hello Gregory, hello all,
I've tested the DB created with hu_HU.UTF8 lc_* settings and it works
like a charm! We'll re-create the database and move the contents. It's
a nice improvement of 8.3 to detect and disallow such
misconfiguration.
--
Summing up the issue & fix (for googling):
- Ve
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Gergely Bor" <[EMAIL PROTECTED]> writes:
>> Environment B: Debian lenny/sid ^[1], kernel version 2.6.20.1, glibc
>> 2.6.1-5, psql 8.2.5, lc_* is hu_HU, all encondings (client, server,
>> DB) are UTF-8.
> I'm not sure this is the right answer but what ha
"Gergely Bor" <[EMAIL PROTECTED]> writes:
> We'll google the initdb stuff and try it ASAP.
>
> What I've tried is LOWER and UPPER, and they seem to return trash for
> Hungarian UTF-8 characters, but they handle ASCII well. (H...
> maybe ILIKE requires LOWER and UPPER to work? Would not be
> i
Hello Gregory,
We'll google the initdb stuff and try it ASAP.
What I've tried is LOWER and UPPER, and they seem to return trash for
Hungarian UTF-8 characters, but they handle ASCII well. (H...
maybe ILIKE requires LOWER and UPPER to work? Would not be
illogical...)
Best regards,
Gerge
"Gergely Bor" <[EMAIL PROTECTED]> writes:
> I have a nasty-looking problem case. Shortly described as follows:
>
> INSERT INTO mytable (id, value) VALUES (4242, 'ĂșabcdĂș');
> SELECT id FROM mytable WHERE value ILIKE '%abc%';
>
> In environment A, the row of the ID just inserted is returned
> correc