Am Dienstag, 19. April 2005 09:18 schrieb Honza Pazdziora:
> Hello,
>
> the nls_string function that makes it possible to sort by arbitrary
> locale has been updated to reflect the changes in error handling in
> PostgreSQL 8.0, due to users using the nls_string sorting on 7.4 and
> requesting it fo
Hello,
the nls_string function that makes it possible to sort by arbitrary
locale has been updated to reflect the changes in error handling in
PostgreSQL 8.0, due to users using the nls_string sorting on 7.4 and
requesting it for 8.0 as well. The distribution can be downloaded from
http://www.
On Thu, Feb 26, 2004 at 09:16:03AM -0500, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > I think possible solution is special function used ORDER BY clause
> > which knows to switch by safe way to wanted locales, convert string by
> > strxfrm() and switch back to backend local
Hi,
a lot of people sometimes need order same data in same DB by more
different locales. For example multi-language web application with DB
in UTF-8. It's problem in PostgreSQL, because PostgreSQL require set
LC_COLLATE by initdb.
I think possible solution is special functio
Karel Zak <[EMAIL PROTECTED]> writes:
> I think possible solution is special function used ORDER BY clause
> which knows to switch by safe way to wanted locales, convert string by
> strxfrm() and switch back to backend locales.
This function breaks the whole backend if an elog() failure o
On Thu, Feb 26, 2004 at 09:16:03AM -0500, Tom Lane wrote:
> Karel Zak <[EMAIL PROTECTED]> writes:
> > I think possible solution is special function used ORDER BY clause
> > which knows to switch by safe way to wanted locales, convert string by
> > strxfrm() and switch back to backend local
Tom Lane <[EMAIL PROTECTED]> writes:
> This function breaks the whole backend if an elog() failure occurs while
> it's got the wrong locale set. I believe it would also be remarkably
> slow --- doesn't setlocale() involve reading a new locale definition
> file from whereever those are stored?
I
