From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Thomas O'Connell <tfo(at)monsterlabs(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org>, <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: [SQL] double precision to numeric overflow error |
Date: | 2003-01-07 23:36:44 |
Message-ID: | 20030107152951.R67168-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
On Tue, 7 Jan 2003, Thomas O'Connell wrote:
> is this expected behavior? if so, then why?
I'd guess so if the timestamp value's integer part is
10 digits long since I believe trying to fit that into
a numeric(15,6) wouldn't work (9 digits . 6 digits).
> db=# create table foo( col timestamp );
> db=# select cast( extract( epoch from col ) as numeric( 15, 6 ) ) from
> foo;
> date_part
> -----------
> (0 rows)
> db=# insert into foo values( current_timestamp );
> INSERT 1705954 1
> db=# select cast( extract( epoch from col ) as numeric( 15, 6 ) ) from
> foo;
> ERROR: overflow on numeric ABS(value) >= 10^9 for field with precision
> 15 scale 6
From | Date | Subject | |
---|---|---|---|
Next Message | Nigel J. Andrews | 2003-01-07 23:49:35 | State of interface modules |
Previous Message | Steve Crawford | 2003-01-07 23:36:10 | Re: [HACKERS] Have people taken a look at pgdiff yet? |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas O'Connell | 2003-01-08 03:01:09 | Re: double precision to numeric overflow error |
Previous Message | Thomas O'Connell | 2003-01-07 23:12:08 | double precision to numeric overflow error |