Is there a reason why Postgres doesn't have Byte or tinyint?

From: Mike Christensen <mike(at)kitchenpc(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Is there a reason why Postgres doesn't have Byte or tinyint?
Date: 2012-01-08 07:05:21
Message-ID: CABs1bs0SJoRbqKH_rJJY+T=Nxxkie-ui-kNvcAOUChpeog2png@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Darren Duncan 2012-01-08 07:22:56 Re: Is there a reason why Postgres doesn't have Byte or tinyint?
Previous Message Tom Lane 2012-01-07 18:37:09 Re: When are SQL functions inlined & how can I tell?