you
Kind regards
Radek Strnad
I think at least case sensitivity can be done by comparing two strings
converted to upper case with toupper() function.
Regards
Radek Strnad
>
> On Tue, Sep 2, 2008 at 2:00 PM, Martijn van Oosterhout <[EMAIL
> PROTECTED]>wrote:
>
>> On Tue, Sep 02, 2008 at 02:50:47PM
Ok, so do you suggest to leave it with a notice "reindex database" or start
to solve it somehow?
Regards
Radek Strnad
On Mon, Sep 1, 2008 at 12:08 AM, Alvaro Herrera
<[EMAIL PROTECTED]>wrote:
> Radek Strnad escribió:
>
> > - when creating database with different col
hesis concerning this
topic where everything will be explained in details so stay tuned.
Regards
Radek Strnad
over these encodings set in chklocale.c. Each
database will be able to use only collations that are created over same
("compatible") encodings regarding encoding_match_list. Each standard
collation (SQL standard) will be defined over all possible encodings
(hard-coded).
Comments?
Rega
When changing databases the database collation will be retrieved from type
text from pg_type. This part should be the only one that will be deleted
when proceeding with phase 2. But that will take a while :-)
Thanks for all your comments
Regards
Radek Strnad
stage I'll
implement function that will use system locales. Adding ICU or any other
library won't be that big deal.
Radek Strnad
On Wed, Jul 2, 2008 at 8:22 PM, Gregory Stark <[EMAIL PROTECTED]>
wrote:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>
> > Alva
or all your replies in advance.
Regards
Radek Strnad
Index: backend/parser/keywords.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/parser/keywords.c,v
retrieving revision 1.194
diff -c -r1.194 keywords.c
*** backend/parser/keywor
Zdenek Kotala wrote:
Radek Strnad napsal(a):
I'm thinking of dividing the problem into two parts - in beginning
pg_collation will contain two functions. One will have hard-coded rules
for these basic collations (SQL_CHARACTER, GRAPHIC_IRV, LATIN1, ISO8BIT,
UCS_BASIC). It will compare
lier pg_database has
been also extended with lc_collate and lc_ctype records that currently
sets lc_collate and lc_ctype per each database.
Please let me know if my idea is right or needs some adjusts. Thank you
Regards
Radek Strnad
--
Sent via pgsql-hackers mailing
ded collations.
Any sugestions?
Radek Strnad
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
11 matches
Mail list logo