Re: Fixed length data types issue

From: Gregory Stark <gsstark(at)mit(dot)edu>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <gsstark(at)mit(dot)edu>, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Martijn van Oosterhout <kleptog(at)svana(dot)org>
Subject: Re: Fixed length data types issue
Date: 2006-09-11 15:37:50
Message-ID: 87r6yiqur5.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:

> > Well it's irrelevant if we add a special data type to handle CHAR(1).
>
> In that case you should probably be using "char" ...

Well "char" doesn't have quite the same semantics as CHAR(1). If that's the
consensus though then I can work on either fixing "char" semantics to match
CHAR(1) or adding a separate type instead.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gevik Babakhani 2006-09-11 15:39:10 Re: help wanted (fmgr.c)
Previous Message Gevik Babakhani 2006-09-11 15:33:12 Re: Proposal for GUID datatype