From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Ian Pilcher <arequipeno(at)gmail(dot)com> |
Cc: | Alexander Gataric <gataric(at)usa(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cast double precision to integer & check for overflow |
Date: | 2013-01-26 23:57:09 |
Message-ID: | 51046D55.1020709@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 01/26/2013 03:09 PM, Ian Pilcher wrote:
> On 01/26/2013 05:06 PM, Alexander Gataric wrote:
>> Just cast to integer. Decimal portion will be lost.
>
> That part I've got. :-)
>
> It's checking that the double precision value will actual fit within the
> range of the integer type (-2147483648 to +2147483647). I could
> certainly hard-code these values, but I'd like to use a more expressive
> syntax, if it is available.
>
http://www.postgresql.org/docs/9.2/interactive/catalog-pg-type.html
production=# SELECT typname,typlen from pg_type where typname ='int8';
-[ RECORD 1 ]-
typname | int8
typlen | 8
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Uckun | 2013-01-27 00:55:05 | Re: Running update in chunks? |
Previous Message | Gavan Schneider | 2013-01-26 23:35:18 | Re: Cast double precision to integer & check for overflow |