Re: [HACKERS] pg_database encoding again

2003-06-02 Thread Tom Lane
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
 What is the encoding of the database names in the pg_database table?  As far
 as I can tell, each row is saved in the encoding of the database from which
 it is created?

That sounds about right.  If you're using databases of different
encodings in the same installation, it would probably be wise to
restrict yourself to the intersection of those encodings when choosing
database names.

I agree that this isn't ideal, but I don't see any way to improve it.
If you like, we could put in code to *enforce* a restriction to 7-bit
ASCII in database names (and user and group names too) ... but that
doesn't seem like a big improvement.

regards, tom lane

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [HACKERS] pg_database encoding again

2003-06-02 Thread Christopher Kings-Lynne
 That sounds about right.  If you're using databases of different
 encodings in the same installation, it would probably be wise to
 restrict yourself to the intersection of those encodings when choosing
 database names.

Bummer.  So there's no one encoding I can set it to :(  Actually, since the
phpPgAdmin interface only allows the creation of databases via the create
database screen, could we just always set it to the encoding of template1?

How do I get the encoding of the server?  Is that the same as the encoding
of template1?

 I agree that this isn't ideal, but I don't see any way to improve it.
 If you like, we could put in code to *enforce* a restriction to 7-bit
 ASCII in database names (and user and group names too) ... but that
 doesn't seem like a big improvement.

I would suggest force Unicode...

Chris


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org


Re: [HACKERS] pg_database encoding again

2003-06-02 Thread Tom Lane
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
 How do I get the encoding of the server?

There is none.  The per-database encodings are the only truth.
We aren't likely to institute one in future, either; the trend
seems to be more towards decentralization than the reverse.

 I would suggest force Unicode...

Seems quite unacceptable to those who aren't using Unicode.

regards, tom lane

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster