| From: | Darren Duncan <darren(at)darrenduncan(dot)net> |
|---|---|
| To: | Mike Christensen <mike(at)kitchenpc(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Is there a reason why Postgres doesn't have Byte or tinyint? |
| Date: | 2012-01-08 07:22:56 |
| Message-ID: | 4F094450.7000102@darrenduncan.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Mike Christensen wrote:
> 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..
Is this just about programmer convenience or is it about space efficiency in the
database? BYTEA might help you. Or try declaring a DOMAIN over SMALLINT that
limits allowed values to the range of a byte. -- Darren Duncan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Christensen | 2012-01-08 07:27:59 | Re: Is there a reason why Postgres doesn't have Byte or tinyint? |
| Previous Message | Mike Christensen | 2012-01-08 07:05:21 | Is there a reason why Postgres doesn't have Byte or tinyint? |