On Wed, 3 Dec 2003, Stephan Szabo wrote:
The locale settings depend on LC_* at initdb time only. When the
postmaster starts it sets the locale based on the stored values from
initdb, not on the current environment.
With an SQL_ASCII database being accessed from a client with
client_encoding
E.Rodichev wrote:
On Wed, 3 Dec 2003, Stephan Szabo wrote:
The locale settings depend on LC_* at initdb time only. When the
postmaster starts it sets the locale based on the stored values from
initdb, not on the current environment.
With an SQL_ASCII database being accessed from a client with
On Thu, 4 Dec 2003, E.Rodichev wrote:
On Wed, 3 Dec 2003, Stephan Szabo wrote:
The locale settings depend on LC_* at initdb time only. When the
postmaster starts it sets the locale based on the stored values from
initdb, not on the current environment.
With an SQL_ASCII database
On Fri, 28 Nov 2003, Tom Lane wrote:
E.Rodichev [EMAIL PROTECTED] writes:
/e:2createdb test
test | er | SQL_ASCII - Incorrect!
(3 rows)
Let's note than the last line is in fact completely incorrect.
What's incorrect about it? You didn't ask for any other encoding
E.Rodichev writes:
It is incorrect, because database test is, really, in KOI8, NOT in SQL_ASCII
in this example, as I explained in my mail.
The encoding is only a declaration of your intentions. What you actually
put into the database is your responsibility.
--
Peter Eisentraut [EMAIL
E.Rodichev wrote:
On Fri, 28 Nov 2003, Tom Lane wrote:
E.Rodichev [EMAIL PROTECTED] writes:
/e:2createdb test
test | er | SQL_ASCII - Incorrect!
(3 rows)
Let's note than the last line is in fact completely incorrect.
What's incorrect about it? You
On Wed, 3 Dec 2003, E.Rodichev wrote:
On Fri, 28 Nov 2003, Tom Lane wrote:
E.Rodichev [EMAIL PROTECTED] writes:
/e:2createdb test
test | er | SQL_ASCII - Incorrect!
(3 rows)
Let's note than the last line is in fact completely incorrect.
What's incorrect
On Wed, 3 Dec 2003, Stephan Szabo wrote:
On Wed, 3 Dec 2003, E.Rodichev wrote:
On Fri, 28 Nov 2003, Tom Lane wrote:
E.Rodichev [EMAIL PROTECTED] writes:
/e:2createdb test
test | er | SQL_ASCII - Incorrect!
(3 rows)
Let's note than the last line is
E.Rodichev wrote:
On Wed, 3 Dec 2003, Stephan Szabo wrote:
On Wed, 3 Dec 2003, E.Rodichev wrote:
On Fri, 28 Nov 2003, Tom Lane wrote:
E.Rodichev [EMAIL PROTECTED] writes:
/e:2createdb test
test | er | SQL_ASCII - Incorrect!
(3 rows)
On Wed, Dec 03, 2003 at 11:42:34PM +0300, E.Rodichev wrote:
On Wed, 3 Dec 2003, Stephan Szabo wrote:
No, it isn't. As far as PostgreSQL is concerned the database is SQL_ASCII
since you didn't override the default encoding at initdb time or at
createdb time. You did choose LC_ values that
On Wed, 3 Dec 2003, E.Rodichev wrote:
On Wed, 3 Dec 2003, Stephan Szabo wrote:
On Wed, 3 Dec 2003, E.Rodichev wrote:
On Fri, 28 Nov 2003, Tom Lane wrote:
E.Rodichev [EMAIL PROTECTED] writes:
/e:2createdb test
test | er | SQL_ASCII - Incorrect!
On Wed, 3 Dec 2003, Alvaro Herrera wrote:
On Wed, Dec 03, 2003 at 11:42:34PM +0300, E.Rodichev wrote:
On Wed, 3 Dec 2003, Stephan Szabo wrote:
No, it isn't. As far as PostgreSQL is concerned the database is SQL_ASCII
since you didn't override the default encoding at initdb time or at
On Wed, 3 Dec 2003, Andrew Dunstan wrote:
Encoding and collation order are two different things. LC_* settings
have no effect on encoding.
see http://www.postgresql.org/docs/current/static/charset.html
I am trying to point out to reverse dependency:
encoding (1) has effect on LC_* settings
On Wed, 3 Dec 2003, Stephan Szabo wrote:
Only the locale settings at initdb time matter. Changing the LC_* later
is not going to change what the database does. Encoding and locale are
separate (but related) and it is your responsibility to make sure the
choices are consistent. If you do not
On Thu, 4 Dec 2003, E.Rodichev wrote:
On Wed, 3 Dec 2003, Stephan Szabo wrote:
Only the locale settings at initdb time matter. Changing the LC_* later
is not going to change what the database does. Encoding and locale are
separate (but related) and it is your responsibility to make sure
E.Rodichev [EMAIL PROTECTED] writes:
/e:2createdb test
test | er | SQL_ASCII - Incorrect!
(3 rows)
Let's note than the last line is in fact completely incorrect.
What's incorrect about it? You didn't ask for any other encoding
than SQL_ASCII.
You can set the default
Hi,
I just noticed some incorrect behaviour for postgresql-7.4 related
to locale.
After installing 7.4 I created database completely from scratch
with cyrillic locale:
su postgres
export LC_CTYPE=ru_RU.KOI8-R
export LC_COLLATE=ru_RU.KOI8-R
/usr/local/pgsql/bin/initdb -D /db2/pgdata
E.Rodichev writes:
I just noticed some incorrect behaviour for postgresql-7.4 related
to locale.
Maybe you should first read the documentation to understand how it
actually works.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of
Le Jeudi 27 Novembre 2003 20:56, E.Rodichev a écrit :
After installing 7.4 I created database completely from scratch
with cyrillic locale:
Dear Evgeny,
If you want to go 'fast', do not hesitate to install pgAdmin3 GUI from
http://www.pgadmin.org. We will be able to create and manage a
After installing 7.4 I created database completely from scratch
with cyrillic locale:
su postgres
export LC_CTYPE=ru_RU.KOI8-R
export LC_COLLATE=ru_RU.KOI8-R
/usr/local/pgsql/bin/initdb -D /db2/pgdata
You need to go:
/usr/local/pgsql/bin/initdb -D /db2/pgdata -E KOI8
To set the default encoding
20 matches
Mail list logo