Re: [RFC] Unsigned integer support. - Mailing list pgsql-hackers

From Dann Corbit
Subject Re: [RFC] Unsigned integer support.
Date
Msg-id D425483C2C5C9F49B5B7A41F8944154701000FAE@postal.corporate.connx.com
Whole thread Raw
In response to Re: [RFC] Unsigned integer support.  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
> -----Original Message-----
> From: Andrew Dunstan [mailto:andrew@dunslane.net]
> Sent: Friday, July 25, 2008 1:28 PM
> To: Dann Corbit
> Cc: Tom Lane; Ryan Bradetich; Gregory Stark; pgsql-
> hackers@postgresql.org
> Subject: Re: [HACKERS] [RFC] Unsigned integer support.
>
>
>
> Dann Corbit wrote:
> >> -----Original Message-----
> >> From: Andrew Dunstan [mailto:andrew@dunslane.net]
> >> Sent: Friday, July 25, 2008 1:11 PM
> >> To: Dann Corbit
> >> Cc: Tom Lane; Ryan Bradetich; Gregory Stark; pgsql-
> >> hackers@postgresql.org
> >> Subject: Re: [HACKERS] [RFC] Unsigned integer support.
> >>
> >>
> >>
> >> Dann Corbit wrote:
> >>
> >>> CREATE DOMAIN usmallint AS SMALLINT CHECK(VALUE > 0);
> >>> CREATE DOMAIN uinteger AS INTEGER CHECK(VALUE > 0);
> >>> CREATE DOMAIN ubigint AS BIGINT CHECK(VALUE > 0);
> >>> CREATE DOMAIN unumeric AS NUMERIC CHECK(VALUE > 0);
> >>>
> >>>
> >>>
> >>>
> >> s/>/>=/g
> >>
> >
> > I turned off the default "option" to remove extra line breaks.
> > Future posts should not be quite as even and bletcherous.
> > God willing, and the crick don't rise.
> >
> >
>
> I suspect you're missing my point, namely that 0 should be an allowed
> value for unsigned types.

Quite right.  The domains I created were really the 'natural numbers'
rather than unsigned types.


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [RFC] Unsigned integer support.
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] odd output in restore mode