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 OAA05406 for ; Sun, 13 Dec 1998 14:33:04 -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 OAA01559; Sun, 13 Dec 1998 14:31:37 -0500 (EST) From: Bruce Momjian Message-Id: <199812131931.OAA01559@candle.pha.pa.us> Subject: Re: [SQL] char type seems the same as char(1) In-Reply-To: <22059.913569250@sss.pgh.pa.us> from Tom Lane at "Dec 13, 1998 12:14:10 pm" To: tgl@sss.pgh.pa.us (Tom Lane) Date: Sun, 13 Dec 1998 14:31:37 -0500 (EST) Cc: lockhart@alumni.caltech.edu, 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 > Bruce Momjian writes: > > Should I add this to the TODO list, that char is not char1 but has > > 4-byte length? > > Well, Tom Lockhart responded that "it's not a bug, it's a feature". > I still think it's broken --- and certainly the fact that quoting > affects the result (char and "char" act differently) is not good. > But the discussion seems to have died out without producing any > definite plan of action. If we use char1 for internal tables, we should allow it externally, if only as char1. I will add it to the TODO list. -- 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