Re: double precision to numeric overflow error

From: Jan Wieck <JanWieck(at)Yahoo(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: double precision to numeric overflow error
Date: 2003-01-17 20:43:31
Message-ID: 3E286AF3.5272F9FA@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-sql

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(at)Yahoo(dot)com #

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Petre Scheie 2003-01-17 21:16:01 [Fwd: FW: Oracle to Postgres data migration -- Please advice.]
Previous Message Tom Lane 2003-01-17 20:20:06 Re: point -> double,double ?

Browse pgsql-sql by date

  From Date Subject
Next Message Wei Weng 2003-01-17 23:51:27 Can I do this?
Previous Message Josh Berkus 2003-01-17 20:16:18 Re: "Best practice" advice