From: Tatsuo Ishii <t-ishii@sra.co.jp>
To: Thomas Lockhart <lockhart@alumni.caltech.edu>
Cc: t-ishii@sra.co.jp, phd2@earthling.net, "'Oleg Bartunov'" <oleg@sai.msu.su>
Cc: 'hackers@postgresql.org' <hackers@postgreSQL.org>
Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem
Date: Thu, 17 Jun 1999 09:53:21 +0900
Message-ID: <199906170053.JAA08805@ext16.sra.co.jp> (raw)
In-Reply-To: <37651B4F.F3B0B6F7@alumni.caltech.edu>
> > Second, the
> > default charset for char and varchar might be implemenation dependent,
> > not neccesarily limited to SQL_TEXT. The only requirement is the
> > charset must contain the repertoire SQL_TEXT has. I think any charsets
> > including ascii I've ever seen satisfies the requirement.
>
> Yow! I certainly misremembered the definition. Date and Darwen, 1997,
> point out that the SQL implementation *must* support at least one
> character set, SQL_TEXT, whose repertoire must contain:
>
> 1) Every character that is used in the SQL language itself (this is
> the part I remembered), and
>
> 2) Every character that is included in *any other character set*
> supported by the SQL implementation (Postgres).
>
> This second requirement is presumably to enable text handling of
> multiple character sets, but would seem to put severe restrictions on
> how we would implement things. Or can it act only as a placeholder,
> allowing us to define new character sets as different types in
> Postgres? Otherwise, we would have to retrofit capabilities into
> SQL_TEXT anytime we defined a new character set??
I don't think so. 2) can be read as:
Any other character set must contain every character included in
SQL_TEXT.
This seems extremely easy to implement. We could define SQL_TEXT be a
subset of ASCII and almost any character set contains ASCII chars. As
a result, any character set satisfies above that is logically same as
2). No?
> > Third, the
> > standards says nothing about locale.
>
> You are referring to the Unix-style system support for "locale"?
Yes.
> Certainly the NCHAR and character set support in SQL92 would qualify
> as locale support in the generic sense...
---
Tatsuo Ishii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: t-ishii@sra.co.jp, lockhart@alumni.caltech.edu, oleg@sai.msu.su, hackers@postgreSQL.org
Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem
In-Reply-To: <199906170053.JAA08805@ext16.sra.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox