Re: Defining a "tinyint" data type - one byte unsigned - Mailing list pgsql-patches

From Shachar Shemesh
Subject Re: Defining a "tinyint" data type - one byte unsigned
Date
Msg-id 404FF48D.2040402@shemesh.biz
Whole thread Raw
In response to Re: Defining a "tinyint" data type - one byte unsigned  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Defining a "tinyint" data type - one byte unsigned
List pgsql-patches
Tom Lane wrote:

>Shachar Shemesh <psql@shemesh.biz> writes:
>
>
>>Attached is a patch to implement "tinyint".
>>
>>
>
>I don't think we've really solved the numeric-hierarchy casting problems
>well enough to be able to stand adding another member of the hierarchy.
>In particular, what impact is this going to have on implicit typing of
>integer constants?
>
>            regards, tom lane
>
>
The nice thing about a one byte integer is that it's at the very bottom
of the food chain. Since casting upwards is implicit and downwards is
explicit, NOTHING casts implicitly to it. As such I'm hoping (like I
said in my original post - I'm no expert) that this will be a harmless
addition.

If there is anything you can think of that will allow me to verify this
claim, do let me know.

--
Shachar Shemesh
Lingnu Open Systems Consulting
http://www.lingnu.com/


pgsql-patches by date:

Previous
From: Shachar Shemesh
Date:
Subject: Re: Defining a "tinyint" data type - one byte unsigned
Next
From: Shachar Shemesh
Date:
Subject: Re: Defining a "tinyint" data type - one byte unsigned