Re: Defining a "tinyint" data type - one byte unsigned

From: Shachar Shemesh <psql(at)shemesh(dot)biz>
To: PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Defining a "tinyint" data type - one byte unsigned
Date: 2004-03-11 05:28:28
Message-ID: 404FF8FC.60809@shemesh.biz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Shachar Shemesh wrote:

> Hmm - replying to my own post.
>
> I did cut one corner, in that I did not implement tiny->int8 and
> tiny->non integers yet. That is, however, an implementation detail
> rather than a principal problem. If that is the whole problem, I'll
> add those as well. I would rather, before doing the extra work, hear
> that this is indeed all that is needed to get it in.

Replying to my own post again!

The documentation for SQL Server says this
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ia-iz_3ss4.asp)

> Functions will return *bigint* only if the parameter expression is a
> *bigint* data type. SQL Server will not automatically promote other
> integer data types (*tinyint*, *smallint*, and *int*) to *bigint*.
>
Perhaps Postgres is not alone with it's casting problems.

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

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Dennis Bjorklund 2004-03-11 06:16:35 Re: Defining a "tinyint" data type - one byte unsigned
Previous Message Shachar Shemesh 2004-03-11 05:17:29 Re: Defining a "tinyint" data type - one byte unsigned