Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 1F2494764FB for ; Fri, 17 Jan 2003 15:45:21 -0500 (EST) Received: from smtp017.mail.yahoo.com (smtp017.mail.yahoo.com [216.136.174.114]) by postgresql.org (Postfix) with SMTP id 5823247637E for ; Fri, 17 Jan 2003 15:45:20 -0500 (EST) Received: from psc.progress.com (HELO Yahoo.com) (janwieck@192.233.92.200 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 17 Jan 2003 20:45:21 -0000 Message-ID: <3E286AF3.5272F9FA@Yahoo.com> Date: Fri, 17 Jan 2003 15:43:31 -0500 From: Jan Wieck Organization: Home X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,ru MIME-Version: 1.0 To: Thomas O'Connell Cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org Subject: Re: double precision to numeric overflow error References: <726.1041999309@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/663 X-Sequence-Number: 35784 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 #