From: | Satoshi Nagayasu <satoshi(dot)nagayasu(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thombrown(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: INTEGER range ("-2147483648" is not accepted.) |
Date: | 2010-06-22 08:59:55 |
Message-ID: | 4C207B8B.4030104@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Magnus,
Thanks for your advice. I've understood how it happens.
However, it looks tricky and difficult to understand,
so I hope that the message could be more understandable
as Thom mentioned.
Regards,
On 2010/06/22 17:48, Thom Brown wrote:
> On 22 June 2010 09:44, Magnus Hagander<magnus(at)hagander(dot)net> wrote:
>> On Tue, Jun 22, 2010 at 10:27 AM, Satoshi Nagayasu
>> <satoshi(dot)nagayasu(at)gmail(dot)com> wrote:
>>> Hi all,
>>>
>>> I've found a bit strange thing on the INTEGER range in the official manual.
>>>
>>> http://www.postgresql.org/docs/8.4/interactive/datatype-numeric.html
>>>
>>> According to the official manual, the INTEGER range is "-2147483648 to +2147483647".
>>> However, my example in below shows that "-2147483648" is not accepted.
>>>
>>> Is this correct? Any suggestions?
>>>
>>> template1=# SELECT -2147483648::integer;
>>> ERROR: integer out of range
>>
>> This gets parsed as "cast 2147483648 to integer
>
> Why? And if so, it would probably be more useful if the error message
> was something more like:
> ERROR: integer 2147483648 out of range
>
> That would at least show the user what the value was seen as by the parser.
>
> Thom
>
--
NAGAYASU Satoshi <satoshi(dot)nagayasu(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-06-22 09:46:30 | Re: INTEGER range ("-2147483648" is not accepted.) |
Previous Message | Thom Brown | 2010-06-22 08:48:49 | Re: INTEGER range ("-2147483648" is not accepted.) |