From: | Sean Chittenden <sean(at)chittenden(dot)org> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
Cc: | CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: int1? |
Date: | 2003-10-09 17:54:53 |
Message-ID: | 20031009175453.GM86551@perrin.nxad.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> > > Is there any date type that can be used for 0-255 values? Like
> > > an "int1" or byte column.
> >
> > A SMALLINT is two bytes on disk, use "char" instead. This is a hidden
>
> However "char" has some serious deficiencies IIRC, such as the fact
> that there's no int<->"char" casts and it's standard I/O format is
> characters. You can use ascii and chr to get around some of that,
> but it's ugly.
*nods* I have explicit casts everywhere when dealing with "char" and
it's far from being elegant or clean.
>
> > goodie in PostgreSQL and one that I wish was exposed via a more
> > conventional syntax (*hint hint*).
>
> If we were going to do that I think we'd be better off making a new
> type and leaving "char" alone.
>
You won't hear any disagreements from me on this one. I've
sufficiently abused "char" as a 1 byte storage field and would love to
see an int1 or tinyint datatype added to cover this situation. -sc
--
Sean Chittenden
From | Date | Subject | |
---|---|---|---|
Next Message | Dann Corbit | 2003-10-09 17:56:31 | Re: Response from MySql AB (Re: Humor me: Postgresql vs. |
Previous Message | Együd Csaba | 2003-10-09 17:50:54 | Re: How to delete unclosed connections? |