Re: BUG #2802: Feature request: tinyint and unsigned types - Mailing list pgsql-bugs

From Jim Nasby
Subject Re: BUG #2802: Feature request: tinyint and unsigned types
Date
Msg-id 23FD7624-3255-4582-A3D4-1E7DB54AE737@decibel.org
Whole thread Raw
In response to Re: BUG #2802: Feature request: tinyint and unsigned types  (Bruno Wolff III <bruno@wolff.to>)
Responses Re: BUG #2802: Feature request: tinyint and unsigned types
List pgsql-bugs
On Dec 4, 2006, at 4:11 PM, Bruno Wolff III wrote:
> You can already use "char" to store 1 byte values, though unless
> there are
> several of these in a row, you won't save any space because of
> alignment.

<nitpick>There's also boolean...</nitpick>

Is there any technical reason why we don't support unsigned ints or
tinyint? Just a matter of no one feeling the itch?
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

pgsql-bugs by date:

Previous
From: "Brien R. Givens"
Date:
Subject: BUG #2818: ADO Field.Attributes reports NULL on NOT NULL fields
Next
From: Tom Lane
Date:
Subject: Re: BUG #2802: Feature request: tinyint and unsigned types