| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Gregory Stark <gsstark(at)mit(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 16:51:39 |
| Message-ID: | 20060911165139.GC28613@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark wrote:
>
> 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.
What semantics? I thought you would just store a byte there, retrieve
it and compare to something else. Anything beyond this doesn't probably
make much sense (to me anyway). Are you thinking in concatenating it, etc?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2006-09-11 17:08:21 | Re: Buildfarm vs. Linux Distro classification |
| Previous Message | Simon Riggs | 2006-09-11 16:28:23 | Re: Fixed length data types issue |