Is there a reason why Postgres doesn't have Byte or tinyint? - Mailing list pgsql-general

From Mike Christensen
Subject Is there a reason why Postgres doesn't have Byte or tinyint?
Date
Msg-id CABs1bs0SJoRbqKH_rJJY+T=Nxxkie-ui-kNvcAOUChpeog2png@mail.gmail.com
Whole thread Raw
Responses Re: Is there a reason why Postgres doesn't have Byte or tinyint?  (Darren Duncan <darren@darrenduncan.net>)
List pgsql-general
According to the manuals, Postgres has smallint (2 byte), integer (4
bytes) and bigint (8 bytes)..  I use a lot of structures with "bytes"
in my code and it's kinda annoying to cast DB output from Int16 to
Byte every time, especially since there's no explicit cast in .NET and
you have to use System.Convert().

Is there a work-around, or do people just cast or use Int16 in their
data structures?  Just wondering..  I know on modern computers it
probably doesn't make any difference anyway..

Mike

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: When are SQL functions inlined & how can I tell?
Next
From: Darren Duncan
Date:
Subject: Re: Is there a reason why Postgres doesn't have Byte or tinyint?