| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Thomas Kellerer" <spam_eater(at)gmx(dot)net>, <pgsql-hackers-win32(at)postgresql(dot)org> |
| Subject: | Re: locales and encodings on Windows |
| Date: | 2004-12-22 12:14:34 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE476431@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
> >> I have no idea, but I'm certain if someone is this is
> definitly not
> >> going to happen for 8.0.
> >
> >
> > I know this feature can't make it into 8.0; but blaming Windows for
> > more than one release cycle might not look very good. :-(
> >
>
> I'm not really experienced with the whole locale/character
> set topic, but what I'm wondering about (and I'm sure others
> will do as well) is, why other databases (such as Firebird or
> Oracle) do support UTF8/Unicode on the Windows platform but
> PostgreSQL does not.
PostgreSQL uses the OS functinos to do locale handling. The other
databases usually implement their own (or use a library that does it,
but they do not rely on the OS)
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-12-22 13:42:39 | Re: 8.0 collate and index use |
| Previous Message | Thomas Kellerer | 2004-12-22 12:12:16 | Re: locales and encodings on Windows |