Tom Lane wrote:
Plan B would be to set the database locale to C, which is
encoding-agnostic and hence allows different databases to have different
encodings. Do you actually need en_US sort order?
I wasn't aware of the difference in sort orders until about two months
ago when i had to comp
Joe <[EMAIL PROTECTED]> writes:
> Going back to my options, are you saying that if I re-initdb the 8.3
> cluster to UTF8, restore the LATIN1 db as UTF8, and then do "set
> client_encoding = LATIN1" in the application code, then everything will
> work fine, even if the machine locale remains en_U
Hi Tom,
Tom Lane wrote:
Why does it have to be LATIN1? If your answer is "my client code deals
in LATIN1", just set client_encoding = LATIN1. You could do that with
ALTER DATABASE SET or possibly ALTER USER SET so that it's transparent
to the clients.
The client code is primarily encoding
Joe <[EMAIL PROTECTED]> writes:
> I can understand that creating a LATIN2, EUC_CN or some other encoding
> in a LATIN1 cluster may cause problems, but don't quite see how UTF-8
> can be a problem since in essence it includes the others. Perhaps
> someone can provide further explanation?
The lo
Hi,
I just run into this bug
(http://archives.postgresql.org/pgsql-bugs/2008-02/msg00010.php). In my
case, Roundup (Python bug tracker) is trying to CREATE DATABASE WITH
ENCODING='UNICODE' in an 8.3.4 cluster created with LATIN1 encoding, and
it gets the error:
encoding UTF8 does not match
Stefan Kunick wrote:
PostgreSQL version: 8.3RC2
Operating system: Windows Longhorn
Description:Create Database with another encoding as the encoding
from postgres
Details:
I installed postgres with the encoding 1252. After this, i started the
program createdb (createdb -E LATIN1 -O p
Stefan Kunick wrote:
> I installed postgres with the encoding 1252. After this, i started the
> program createdb (createdb -E LATIN1 -O postgres -p -U postgres). The
> program stopped with the error message: createdb: database creation failed.
> Error: encoding LATIN1 does not match server's l
The following bug has been logged online:
Bug reference: 3924
Logged by: Stefan Kunick
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3RC2
Operating system: Windows Longhorn
Description:Create Database with another encoding as the encoding
from postgres
Detail
