| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | crocket <crockabiscuit(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Is there any plan to add unsigned integer types? |
| Date: | 2011-09-26 10:55:12 |
| Message-ID: | 1317034512.1759.14.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On mån, 2011-09-26 at 19:41 +0900, crocket wrote:
> MySQL already has unsigned INT type, and it has double the range of
> signed INT type.
> It's not just the bigger range that UINT type brings.
> If unsigned INT type exists, I wouldn't have to execute "create domain
> UINT" in every database.
>
> If "INT unsigned" and "SERIAL unsigned" exist, PostgreSQL would bring
> more convenience to users.
>
I believe there have been many discussions about this in the past,
outlining the various issues that would come with this project. A first
step would be to start implementing this in user space and see how much
breaks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-09-26 11:12:42 | Re: Support UTF-8 files with BOM in COPY FROM |
| Previous Message | Peter Eisentraut | 2011-09-26 10:52:23 | Re: [v9.2] make_greater_string() does not return a string in some cases |