Received: from ext16.sra.co.jp (IDENT:root@ykh28DS11.kng.mesh.ad.jp [133.205.214.11]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA90567 for ; Mon, 14 Jun 1999 10:13:42 -0400 (EDT) (envelope-from t-ishii@ext16.sra.co.jp) Received: from ext16.sra.co.jp (t-ishii@localhost [127.0.0.1]) by ext16.sra.co.jp (8.8.8/8.8.8) with ESMTP id XAA00874; Mon, 14 Jun 1999 23:07:09 +0900 Message-Id: <199906141407.XAA00874@ext16.sra.co.jp> To: Thomas Lockhart cc: phd2@earthling.net, "'Oleg Bartunov'" , "'hackers@postgresql.org'" , Tatsuo Ishii Subject: Re: [HACKERS] Postgres 6.5 beta2 and beta3 problem From: Tatsuo Ishii Reply-To: t-ishii@sra.co.jp In-reply-to: Your message of Fri, 11 Jun 1999 15:23:57 GMT. <37612A0D.BAF8B997@alumni.caltech.edu> Date: Mon, 14 Jun 1999 23:07:08 +0900 Sender: t-ishii@ext16.sra.co.jp > OK, SQL92 defines two kinds of native character sets: those we already > have (char, varchar) and those which can be locale customized (nchar, > national character varying, and others). char and varchar always > default to the "SQL" behavior (which I think corresponds to ascii > (called "SQL_TEXT") but I didn't bother looking for the details). This seems to be a little bit different from the standard. First, SQL_TEXT is not equal to ascii. It's a subset of ascii. 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. Third, the standards says nothing about locale. --- Tatsuo Ishii