Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.1/8.9.1) with ESMTP id WAA07453 for ; Sun, 13 Dec 1998 22:58:22 -0500 (EST) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id WAA06630; Sun, 13 Dec 1998 22:56:29 -0500 (EST) From: Bruce Momjian Message-Id: <199812140356.WAA06630@candle.pha.pa.us> Subject: Re: [SQL] char type seems the same as char(1) In-Reply-To: <367465A8.B0F8E327@alumni.caltech.edu> from "Thomas G. Lockhart" at "Dec 14, 1998 1:11: 4 am" To: lockhart@alumni.caltech.edu (Thomas G. Lockhart) Date: Sun, 13 Dec 1998 22:56:29 -0500 (EST) Cc: tgl@sss.pgh.pa.us, pgsql-sql@hub.org X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > > > If we use char1 for internal tables, we should allow it > > > > externally, if only as char1. I will add it to the TODO list. > > > As what? > > As "char1", of course. > > Oh well. Thought that there might be other solutions, that's all... Well, since ansi wants char to be char(1) and to be like that other char's, I don't think we have a choice but to choose another name. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026