From: Bruce Momjian <maillist@candle.pha.pa.us>
To: tgl@sss.pgh.pa.us
Cc: lockhart@alumni.caltech.edu
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] char type seems the same as char(1)
Date: Sun, 13 Dec 1998 14:31:37 -0500 (EST)
Message-ID: <199812131931.OAA01559@candle.pha.pa.us> (raw)
In-Reply-To: <22059.913569250@sss.pgh.pa.us>
> Bruce Momjian <maillist@candle.pha.pa.us> 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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: maillist@candle.pha.pa.us, tgl@sss.pgh.pa.us, lockhart@alumni.caltech.edu, pgsql-sql@hub.org
Subject: Re: [SQL] char type seems the same as char(1)
In-Reply-To: <199812131931.OAA01559@candle.pha.pa.us>
References: <22059.913569250@sss.pgh.pa.us> <199812131931.OAA01559@candle.pha.pa.us>
* 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