Ð ÐÑÑ, 20.07.2004, Ð 16:52, PostgreSQL Bugs List ÐÐÑÐÑ:
> I have DB under UTF8. A field of my table have btree index. But this index
> works incorrectly if this field content localized data. For example, how you
> can explain this:
>
> select object_id, name from main_objects where name='ÐÑ
bug=# select * from example_objects where name = 'ÐÑ';
object_id | name
---+
2 | ÐÑ
2 | ÐÑ
(ÑÐÐ: 2)
bug=# select version();
version
Am Freitag, 23. Juli 2004 11:49 schrieb Markus Bertheau:
> Do the following in an installation initdb'd in ru_RU.KOI8-R (It doesn't
> happen if you initdb'd with UTF-8). You need to run psql in a locale
> that is capable of russian letters, namely an UTF-8 locale, or a KOI8-R
> locale. Then:
>
> CR
Ð ÐÑÐ, 23.07.2004, Ð 14:02, Peter Eisentraut ÐÐÑÐÑ:
> Am Freitag, 23. Juli 2004 11:49 schrieb Markus Bertheau:
> > Do the following in an installation initdb'd in ru_RU.KOI8-R (It doesn't
> > happen if you initdb'd with UTF-8). You need to run psql in a locale
> > that is capable of russian letters
Markus Bertheau <[EMAIL PROTECTED]> writes:
> Do the following in an installation initdb'd in ru_RU.KOI8-R (It doesn't
> happen if you initdb'd with UTF-8).
If this is a bug, it's a bug in the ru_RU.KOI8-R locale definition.
You can prove that the locale considers the strings equal without
Postgre
Am Freitag, 23. Juli 2004 15:30 schrieb Markus Bertheau:
> > That's your problem. Your locale doesn't match your encoding. You need
> > to use a compatible combination.
>
> What is happening in the server that this is required?
When you ask locale-aware functions to compare strings, convert to l
Consider the following example for 7.4.3
% cat test.sql
CREATE SCHEMA test_schema;
SET search_path TO test_schema;
CREATE TABLE test_table (
x serial,
s bigint
) WITHOUT OIDS;
CREATE FUNCTION test_update_s() RETURNS trigger AS '
BEGIN
SELECT INTO NEW.s sum(x) F
On Sat, Jul 24, 2004 at 01:56:02AM +0400, Alexander M. Pravking wrote:
> But the following works:
>
> [EMAIL PROTECTED] SET search_path TO test_schema;
> SET
> [EMAIL PROTECTED] INSERT INTO test_table DEFAULT VALUES ;
> INSERT 0 1
> [EMAIL PROTECTED] SET search_path TO public;
> SET
> [EMAIL PROTE
