Re: double precision to numeric overflow error - Mailing list pgsql-general

From Jan Wieck
Subject Re: double precision to numeric overflow error
Date
Msg-id 3E286AF3.5272F9FA@Yahoo.com
Whole thread Raw
In response to Re: double precision to numeric overflow error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thomas O'Connell wrote:
>
> 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 much worth
> assigned to error reporting:

The message will be exactly the same in all cases, since there is no
more detail. I think words about casting and such could be fairly
confusing in the case someone just inserts a literal value - no?


Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: point -> double,double ?
Next
From: Sean Chittenden
Date:
Subject: pg_stat_get_backen_last_activity() ???