| From: | Hannu Krosing <hannu(at)trust(dot)ee> |
|---|---|
| To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Cc: | 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-09 19:04:00 |
| Message-ID: | 375EBAA0.D5DE4B2E@trust.ee |
| 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.
-------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 1999-06-09 19:28:19 | Re: [HACKERS] PL/Lang (was: Priorities for 6.6) |
| Previous Message | Hannu Krosing | 1999-06-09 18:32:03 | Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem |