On tis, 2010-08-17 at 01:16 -0500, Jaime Casanova wrote:
creating collations ...FATAL: invalid byte sequence for encoding
UTF8: 0xe56c09
CONTEXT: COPY tmp_pg_collation, line 86
STATEMENT: COPY tmp_pg_collation FROM
E'/usr/local/pgsql/9.1/share/locales.txt';
Hmm, what is in that
On Wed, Aug 18, 2010 at 11:29 AM, Peter Eisentraut pete...@gmx.net wrote:
On tis, 2010-08-17 at 01:16 -0500, Jaime Casanova wrote:
creating collations ...FATAL: invalid byte sequence for encoding
UTF8: 0xe56c09
CONTEXT: COPY tmp_pg_collation, line 86
STATEMENT: COPY tmp_pg_collation
On Mon, Aug 16, 2010 at 10:56 PM, Peter Eisentraut pete...@gmx.net wrote:
On lör, 2010-08-14 at 02:05 -0500, Jaime Casanova wrote:
BTW, why the double quotes?
Because the name contains upper case letters?
why everything seems so obvious once someone else state it? :)
sorry to state the
On lör, 2010-08-14 at 02:05 -0500, Jaime Casanova wrote:
btw, the patch no longer apply cleanly but most are just hunks the
worst it's in src/backend/catalog/namespace.c because
FindConversionByName() is now called get_conversion_oid()... so maybe
this function should be named
Hi,
sorry for the delay...
btw, the patch no longer apply cleanly but most are just hunks the
worst it's in src/backend/catalog/namespace.c because
FindConversionByName() is now called get_conversion_oid()... so maybe
this function should be named get_collation_oid(), i guess
On Tue, Aug 3, 2010
On mån, 2010-08-02 at 01:43 -0500, Jaime Casanova wrote:
nowadays, CREATE DATABASE has a lc_collate clause. is the new collate
clause similar as the lc_collate?
i mean, is lc_collate what we will use as a default?
Yes, if you do not specify anything per column, the database default is
used.
On Tue, Jul 13, 2010 at 1:25 PM, Peter Eisentraut pete...@gmx.net wrote:
Here is a proof of concept for per-column collation support.
Hi,
i was looking at this.
nowadays, CREATE DATABASE has a lc_collate clause. is the new collate
clause similar as the lc_collate?
i mean, is lc_collate what
On tor, 2010-07-15 at 05:57 +0200, Pavel Stehule wrote:
:( maybe we have to enhance a locales - or do some work in this way.
In Czech's IS is relative often operation some like
name = 'Stěhule' COLLATION cs_CZ_cs_ai -- compare case insensitive
accent insensitive
PostgreSQL is last db,
Peter Eisentraut pete...@gmx.net writes:
Well, the comparison function varstr_cmp() contains this comment:
/*
* In some locales strcoll() can claim that nonidentical strings are
* equal. Believing that would be bad news for a number of reasons,
* so we follow Perl's lead
On Thu, Jul 15, 2010 at 4:24 PM, Tom Lane t...@sss.pgh.pa.us wrote:
The problem with not doing that is it breaks hashing --- hash joins and
hash aggregation being the real pain points.
citext works around this in a rather klugy fashion by decreeing that two
strings are equal iff their
Peter Eisentraut pete...@gmx.net wrote:
Here is a proof of concept for per-column collation support.
Did you want a WIP review of that patch? (CF closing to new
submissions soon)
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Hello
I have only one question - If I understand well you can use collate
just for sort. What is your plan for range search operation? Sort is
interesting and I am sure important for multilangual applications, for
me - more important is case sensitive, case insensitive, accent
sensitive,
On ons, 2010-07-14 at 19:35 +0200, Pavel Stehule wrote:
I have only one question - If I understand well you can use collate
just for sort. What is your plan for range search operation?
My patch does range searches. Sorting uses the same operators, so both
will be supported. (Sorting is not
2010/7/14 Peter Eisentraut pete...@gmx.net:
On ons, 2010-07-14 at 19:35 +0200, Pavel Stehule wrote:
I have only one question - If I understand well you can use collate
just for sort. What is your plan for range search operation?
My patch does range searches. Sorting uses the same operators,
14 matches
Mail list logo
