From my point of view (administrators view, not developers) it is such
a drawback
in postgres implementation that it seriously challenges the position as
a competitor
to the big dragons. (IF they suffer from the same missing feature)
Recreating indicies is maybe not great but can be done quit e
Jonas Forsman wrote:
Recreating indicies is maybe not great but can be done quit easily compared
to reinitializing a db or recoding an entire database.
Sometimes a bit of a solution is all what it is needed. Would it be
possible
to change the locale on the fly and only recreate indicies afterwa
(please keep the list cc'd)
Jonas Forsman wrote:
if I cannot change charset within a postgres installation
and then benefit from all the features in postgres isn't that to be seen
as a bug
or at least it should be a workaround easier than dumping everything
which I think is a too large risk to
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Jonas Forsman wrote:
>
>> Try:
>> select * from table where lower(address) like '%Ã¥%'
>>
>> This select fails to find addresses including capital Ã… and similars in
>> LATIN1 (like Å, Ä, Ö).
Isn't à an upper-case letter? In which case lower
Jonas Forsman wrote:
it is possibly a locale-error. may I ask:
1. How do I check the locale?
Within psql:
show lc_ctype; (and other lc_* variables as well)
show server_encoding;
show client_encoding;
2. Can I change this on already running db:s ?
Unfortunately you can't. You'll have to re-
Jonas Forsman wrote:
The following bug has been logged online:
Bug reference: 3737
Logged by: Jonas Forsman
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.10
Operating system: Ubuntu 6.06 LTS
Description:lower/upper fails to match extended chars in LATIN1
The following bug has been logged online:
Bug reference: 3737
Logged by: Jonas Forsman
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.10
Operating system: Ubuntu 6.06 LTS
Description:lower/upper fails to match extended chars in LATIN1
Details:
Try:
select
