On Tue, 2005-02-15 at 14:33 +0100, Peter Eisentraut wrote:
> Am Dienstag, 15. Februar 2005 10:22 schrieb Karel Zak:
> > in PG: unicode = utf8 = utf-8
> >
> > Our internal routines in src/backend/utils/mb/encnames.c accept all
> > synonyms. The "official" internal PG name for UTF-8 is "UNICODE" :-(
>
> I think in the SQL standard the official name is UTF8. If someone wants to
> verify that this is the case and is exactly the encoding we offer (perhaps
> modulo the 0x10000 issue), then it might make sense to change the canonical
> form to UTF8.
Yes, I think we should fix it and remove UNICODE and WIN encoding names
from PG code.
Karel
--
Karel Zak <[EMAIL PROTECTED]>
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
