| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_database encoding again |
| Date: | 2003-06-02 04:33:23 |
| Message-ID: | 135201c328c0$1a780150$6500a8c0@fhp.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-06-02 04:35:09 | Re: Dev FAQ emacs settings |
| Previous Message | Tom Lane | 2003-06-02 04:11:31 | Re: pg_database encoding again |