Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.1/8.9.1) with ESMTP id MAA25584 for ; Sun, 13 Dec 1998 12:15:44 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id MAA22061; Sun, 13 Dec 1998 12:14:10 -0500 (EST) To: Bruce Momjian cc: lockhart@alumni.caltech.edu, pgsql-sql@hub.org Subject: Re: [SQL] char type seems the same as char(1) In-reply-to: Your message of Sat, 12 Dec 1998 22:41:09 -0500 (EST) <199812130341.WAA12919@candle.pha.pa.us> Date: Sun, 13 Dec 1998 12:14:10 -0500 Message-ID: <22059.913569250@sss.pgh.pa.us> From: Tom Lane 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. regards, tom lane