From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | CSN <cool_screen_name90001(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dumb question about serial's upper limit |
Date: | 2005-10-11 23:32:21 |
Message-ID: | 20051011233221.GQ23883@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Oct 11, 2005 at 02:22:23AM -0400, Tom Lane wrote:
> "Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> > Out of curiosity... why don't we have unsigned ints?
>
> Quick, is 42 an int or an unsigned int?
>
> I think it'd create a slew of new ambiguous cases in the
> numeric-datatype hierarchy, for what is really pretty darn small gain.
> We're already just barely getting by the problem that 42 might be
> intended as an int2 or int8 constant --- and at least those three
> datatypes have compatible comparison semantics, so that there aren't any
> fundamental semantic problems created if you decide that a constant is
> one or the other. Adding unsigned types to the mix seems to me to be
> likely to cause some serious issues.
Couldn't the same logic of starting with the most restrictive case and
working up work here as well?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Hallstrom | 2005-10-11 23:51:49 | Re: [GENERAL] Oracle buys Innobase |
Previous Message | Jim C. Nasby | 2005-10-11 23:30:27 | Re: Dumb question about serial's upper limit |