From: | Stefan Leitich <steffn(at)gmx(dot)at> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: order by a string |
Date: | 2003-10-15 11:26:44 |
Message-ID: | 3F8D2EF4.8080406@gmx.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
so the only way i come around this problem is dump my db. drop the db.
and do a initdb with the right settings and run my dump on the new one?
how can i figure out which locale is set on the suse machine (i am a
linux novice, sorry)?
which locale i should set on the suse machine for use in a german
language environment, and how do i do it?
thanx for your help!
stefan
Peter Eisentraut wrote:
>Stefan Leitich writes:
>
>
>
>>i am developing with version 7.3.2 under cygwin. my production
>>evironment is 7.3.3 on a suse machine.
>>language settings (lc_...) for the server are on developing and
>>production machine the same, 'C'.
>>now i encoutered the following behaviour. i use a union select to unify
>>a query result with an ' (all)' entry.
>>i used at home a space on first character to ensure this entry will be
>>on top if i am ordering by the column.
>>it works in developing environment but it doesnt in production. in
>>production i got a ordering result wich ignores special chars like my
>>whitespace and the '(' and the all entry so comes for example after
>>'akk' and before 'amm'.
>>
>>
>
>That is a pretty clear indication that the locale on the production
>machine is not, in fact, C. Note that the locale is set when the cluster
>is initialized, so you may need to re-initdb.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Fromm | 2003-10-15 12:38:02 | Re: PG tools |
Previous Message | Mike Leahy | 2003-10-15 10:21:24 | Re: Indexes? |