Yes. I'm sure that we are using LATIN1 on both. ServerA works, but ServerB not.
We changed the local of ServerA(as it is a testing server) the same as ServerB,
but ServerA still works. Quite strange.
Pavel Stehule <[EMAIL PROTECTED]> wrote: Hello
> Are you sure you're using LATIN1 on both?
>
>
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> On 21/01/2008, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
>> Pavel Stehule wrote:
>>> when database uses different encoding, than is specified in cluster's
>>> initialization, then lower, upper doesn't work.
>>
>> Oooh. That's... confusing.
> yes, po
On 21/01/2008, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
> Pavel Stehule wrote:
> > when database uses different encoding, than is specified in cluster's
> > initialization, then lower, upper doesn't work.
>
> Oooh. That's... confusing.
yes, postgresql support different encodings, but this confi
Hello
> Are you sure you're using LATIN1 on both?
>
> js=# \l
> List of databases
> Name| Owner | Encoding
> ---+--+--
> js| cww | UTF8
> test | cww | LATIN1
> [ ...snip... ]
>
> js=# SELECT lower('ÉÈ');
> lower
> ---
>
Pavel Stehule wrote:
when database uses different encoding, than is specified in cluster's
initialization, then lower, upper doesn't work.
Oooh. That's... confusing.
Colin
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will
Hello
On 21/01/2008, lan ping <[EMAIL PROTECTED]> wrote:
> Hi, there
>
> In our database, some customers' names contain French accent like
> É,é,È,è. In one server, case-insensitive search works for capital letters.
> For example,
> SELECT lower('ÉÈ') could return éè . But the other server cannot
lan ping wrote:
Hi, there
In our database, some customers' names contain French accent like
É,é,È,è. In one server, case-insensitive search works for capital
letters. For example,
SELECT lower('ÉÈ') could return éè . But the other server cannot.
It is very strange, as the two server use the
