| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Dennis Gearon <gearond(at)fireserve(dot)net> |
| Cc: | Greg Stark <gsstark(at)MIT(dot)EDU>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Collation rules and multi-lingual databases |
| Date: | 2003-08-21 00:19:35 |
| Message-ID: | 87d6ezkgko.fsf@stark.dyndns.tv |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dennis Gearon <gearond(at)fireserve(dot)net> writes:
> I think it would be nice, and I may write it eventually, to have a function
> called:
>
> COLLATION_VALUE( 'string', 'encoding' )
Indeed that would be really nice. I wish I had that and a pony.
Unfortunately my understanding is that the collation rules are simply too
complex to allow such a function in general. It's too bad because it would
indeed eliminate a lot of the problems in a single swoop.
Hm. But perhaps I can come up with such a function for the few collation
domains I care about. I think English is just a matter of making it case
insensitive, and fr_xx is just a matter of squashing accents. In which case I
should be able to do it myself.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2003-08-21 01:29:08 | Re: Buglist |
| Previous Message | Jeff Davis | 2003-08-20 23:26:26 | query optimization: aggregate and distinct |