From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hannu Krosing <hannu(at)trust(dot)ee> |
Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, ZEUGSWETTER Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at>, "'hackers(at)postgresql(dot)org'" <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem |
Date: | 1999-06-10 00:54:38 |
Message-ID: | 199906100054.UAA14722@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Oleg Bartunov wrote:
> >
> >
> > Thanks for explanations. It would be great if I could specify for specific
> > columns if it needs locale. For now I have to pay decreasing in speed
> > just to enable locale for the only column of one database !!!
> > I always dream to be able to specify on fly 'SET LOCALE to ON|OFF'
> > It's a bit separate problem, but probably more easy to implement.
>
> Actually the locale should be part of field definition (like length and
> precision currently are) with default of ascii.
>
> And also it may be probably safest to maintain our own locale defs (as
> Oracle
> currently does)so that things don't break if somebody changes the system
> ones.
Added to TODO:
* Allow LOCALE on a per-column basis, default to ASCII
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-06-10 00:56:42 | UNION + GROUP BY bug located |
Previous Message | Bruce Momjian | 1999-06-10 00:51:04 | Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem |