> Oh. I was recalling SQL_TEXT as being a "subset" character set which
> contains only the characters (more or less) that are required for
> implementing the SQL92 query language and standard features.
>
> Are you seeing it as being a "superset" character set which can
> represent all other character sets??
Yes, it's my understanding from the section 19.3.1 of Date's book
(fourth edition). Please correct me if I am wrong.
> And, how would you suggest we start tracking this discussion in a design
> document? I could put something into the developer's guide, or we could
> have a plain-text FAQ, or ??
>
> I'd propose that we start accumulating a feature list, perhaps ordering
> it into categories like
>
> o required/suggested by SQL9x
> o required/suggested by experience in the real world
> o sure would be nice to have
> o really bad idea ;)
Sounds good. Could I put "CREATE CHARACTER SET" as the first item of
the list and start a discussion for that?
I have a feeling that you have an idea to treat user defined charset
as a PostgreSQL new data type. So probably "CREATE CHARACTER SET"
could be traslated to our "CREATE TYPE" by the parer, right?
--
Tatsuo Ishii
