Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 31147 invoked from network); 27 Jan 2008 01:13:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jan 2008 01:13:19 -0000 Received: (qmail 52558 invoked by uid 500); 27 Jan 2008 01:13:09 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 52102 invoked by uid 500); 27 Jan 2008 01:13:08 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 52091 invoked by uid 99); 27 Jan 2008 01:13:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Jan 2008 17:13:08 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hongcodes@gmail.com designates 209.85.146.177 as permitted sender) Received: from [209.85.146.177] (HELO wa-out-1112.google.com) (209.85.146.177) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Jan 2008 01:12:42 +0000 Received: by wa-out-1112.google.com with SMTP id m38so2200293waf.5 for ; Sat, 26 Jan 2008 17:12:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=KPbwI8xZCkJfSpNiq9s4GqXK/q23+UbBOEB1BY2yI6E=; b=RPhE+toa91A2AXnMF3fzfyzCOF42cKorHgUINwLDSNedPwOMVI+39jUs+QtSwHjYNncOzhmyF5Lc5BoccQb6Wzcsp7fHxUcnXPAV8zJKaWW5+nFmaUnP49lzSqm54EfDfNBFazarZ1R08uupn7I0UssaryRaqRu7P52d6D2BgvA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=xn/Lktl6ltaG5X+/dsgp248SjpriR0xrOfft3jWkYN7P88XJuKmKV21m7XxjjNDF951XZPPNQpFpO0zwLYLbTZom30RacTiwnpqD6uvPhZi3N8y1XKjffO7qywSP6ycAQRMBzBegHxwMSTKSB2Txe8vCx/+s/k8kDZvCyhTSn10= Received: by 10.114.134.1 with SMTP id h1mr4398068wad.4.1201396368882; Sat, 26 Jan 2008 17:12:48 -0800 (PST) Received: by 10.114.38.7 with HTTP; Sat, 26 Jan 2008 17:12:48 -0800 (PST) Message-ID: Date: Sat, 26 Jan 2008 17:12:48 -0800 From: "Hong Ji" To: "Derby Discussion" Subject: java.sql.SQLDataException: The resulting value is outside the range for the data type DOUBLE. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4182_10883327.1201396368876" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_4182_10883327.1201396368876 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline When inserting a record with a DOUBLE field and value Double.MAX_VALUE, it generates the exception \: java.sql.SQLDataException: The resulting value is outside the range for the data type DOUBLE. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedResultSet.noStateChangeException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.setDouble(Unknown Source) ... Not all the DOUBLE fields fail with value Double.MAX_VALUE. I googled it and similar issue was mentioned years. Not sure, if it is still a bug? We are using Derby 10.3.1.4. Regards, Hong ------=_Part_4182_10883327.1201396368876 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline When inserting a record with a DOUBLE field and value Double.MAX_VALUE, it generates the exception \:

java.sql.SQLDataException: The resulting value is outside the range for the data type DOUBLE.
        at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedResultSet.noStateChangeException(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedPreparedStatement.setDouble(Unknown Source)
        ...

Not all the DOUBLE fields fail with value Double.MAX_VALUE.

I googled it and similar issue was mentioned years. Not sure, if it is still a bug?
We are using Derby 10.3.1.4.

Regards,
Hong
------=_Part_4182_10883327.1201396368876--