Re: [SQL] double precision to numeric overflow error

2003-01-07 Thread Thomas O'Connell
Well, it would've immediately (rather than the several minutes it took) given away the problem if it read something like: ERROR: overflow caused by cast of double precision value to numeric without sufficient precision, scale (15, 6) or even, depending on how much detail is available or how mu

Re: [SQL] double precision to numeric overflow error

2003-01-07 Thread Thomas O'Connell
Indeed, it seems as though my inability to count digits was the real problem. Still, does this not strike anyone as a somewhat abstruse error message? -tfo In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Stephan Szabo) wrote: > On Tue, 7 Jan 2003, Thomas O'Connell wrote: > > > is this exp

Re: [SQL] double precision to numeric overflow error

2003-01-07 Thread Stephan Szabo
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 ); >