Return-Path: X-Original-To: apmail-empire-db-user-archive@www.apache.org Delivered-To: apmail-empire-db-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F0F31139C for ; Thu, 18 Sep 2014 10:37:39 +0000 (UTC) Received: (qmail 66502 invoked by uid 500); 18 Sep 2014 10:37:39 -0000 Delivered-To: apmail-empire-db-user-archive@empire-db.apache.org Received: (qmail 66494 invoked by uid 500); 18 Sep 2014 10:37:38 -0000 Mailing-List: contact user-help@empire-db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@empire-db.apache.org Delivered-To: mailing list user@empire-db.apache.org Received: (qmail 66484 invoked by uid 99); 18 Sep 2014 10:37:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 10:37:38 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ivan.nemeth@gmail.com designates 209.85.192.41 as permitted sender) Received: from [209.85.192.41] (HELO mail-qg0-f41.google.com) (209.85.192.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 10:37:12 +0000 Received: by mail-qg0-f41.google.com with SMTP id a108so805277qge.0 for ; Thu, 18 Sep 2014 03:37:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=GwvAvJ2IjL1dwb9H8o8ueRE+Ymz1RUor97b1TyJ8aV8=; b=bR0RKjyX8+g9LjK0TJ5RbXyoYc1PXl+QROXHpWS6XOhfdqzfvd8JIBUBtzmM2eoBGq zu1WjEFflpBhWm83F0mUwX6pAlDegBo5iWjTpfwJiOfwJVUYrMNxWOujqk/LBgu34eLS S0W5kVrWuHYPmBaq9g06VZPfT2E6j7gbXxkksa6NaZIhpNgw4ndVnY4EUK7jwiPBTqav jC2DgDw9WF1ebEz+fdEN3c5oC/qeQnk6nxIAj6t6FHu7Or9xbQRGJs12c5WV7q64bYZv +l8oyiQ2r4SlHNhsId3+g1GKwbA14JkKCxAPLECshz6+CA+35DPu0x8WKiiAcy8x6LSc aaMg== X-Received: by 10.236.45.65 with SMTP id o41mr1436585yhb.118.1411036631402; Thu, 18 Sep 2014 03:37:11 -0700 (PDT) MIME-Version: 1.0 Sender: ivan.nemeth@gmail.com Received: by 10.170.174.65 with HTTP; Thu, 18 Sep 2014 03:36:51 -0700 (PDT) In-Reply-To: References: From: ivan nemeth Date: Thu, 18 Sep 2014 12:36:51 +0200 X-Google-Sender-Auth: DX8FagXL5krReBYgiV2MA8I-XmY Message-ID: Subject: Re: Decimal Datatype with scale 10 To: user Content-Type: multipart/alternative; boundary=089e0115ef7a2e0e5705035491e7 X-Virus-Checked: Checked by ClamAV on apache.org --089e0115ef7a2e0e5705035491e7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Rainer, thanks for the info. We're developing financial applications for fund management companies and prices are stored with scale 10 in our databases, and so our code is based on this. It will be a lot of work to change it in our code, so if it will be fixed it's a good news for me. (Until then I subclassed DBTableColumn which overrides the validateNumber method, which caused the main problem.) Other question regarding DECIMAL types.Why does the the DBRowSetData.getDecimal() method return BigDecimal.ZERO (and not null like in Java ResultSet) when the db value is NULL? There is a clear difference between a null value and a ZERO value. Thanks, Ivan On Thu, Sep 18, 2014 at 9:05 AM, Rainer D=C3=B6bele wro= te: > Hi Ivan, > > > > this issue has already been reported. > > Here=E2=80=99s the corresponding JIRA ticket: > > https://issues.apache.org/jira/browse/EMPIREDB-208 > > > > At the moment I cannot offer a solution but we=E2=80=99re working on it. > > > > Just for curiosity: > > What application do you need that for? > > i.e. what kind of information are you storing in that decimal and why do > you need such long scales? > > > > Regards > > Rainer > > > > > > *from:* ivan.nemeth@gmail.com [mailto:ivan.nemeth@gmail.com] *Im Auftrag > von *ivan nemeth > *to:* user > *re:* Decimal Datatype with scale 10 > > > > Hi, > > > > how can I define a DECIMAL column with scale 10? > > > > Thanks, > > Ivan > --089e0115ef7a2e0e5705035491e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Rainer,

thanks for the info.

We're developing financial applications for fund mana= gement companies and prices are stored with scale 10 in our databases, and = so our code is based on this. =C2=A0It will be a lot of work to change it i= n our code, so if it will be fixed it's a good news for me. (Until then= I subclassed DBTableColumn which overrides the validateNumber method, whic= h caused the main problem.)

Other question regardi= ng DECIMAL types.Why does the the DBRowSetData.getDecimal() method =C2=A0re= turn BigDecimal.ZERO (and not null like in Java ResultSet) when the db valu= e is NULL? There is a clear difference between a null value and a ZERO valu= e.

Thanks,=C2=A0
Ivan



On Thu, Sep 18, 2014 at 9:05 AM, Rainer D=C3=B6bele <doebele@esteam.= de> wrote:

Hi Ivan,

=C2=A0

<= span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:"Calibri&quo= t;,"sans-serif";color:#1f497d">this issue has already been report= ed.

Here=E2=80=99s the corresponding JIRA ticket:

https://issues.apache.org/jira/browse/EMPIREDB-208

=C2=A0

At the moment I cannot offer a solution but we=E2= =80=99re working on it.

=C2=A0

Just for curiosi= ty:

What application do you need that for?

i.e.= what kind of information are you storing in that decimal and why do you ne= ed such long scales?

=C2=A0

Regards

<= p class=3D"MsoNormal">Rainer

=C2=A0

=C2=A0

from: ivan.nemeth@gmail.com [mail= to:ivan.nemeth@g= mail.com] Im Auftrag von ivan nemeth
to: user
re= : Decimal Datatype with scale 10

=C2=A0

Hi,

=C2=A0

how can I define a DEC= IMAL=C2=A0column=C2=A0with scale 10?

=C2=A0

Th= anks,

Ivan=


--089e0115ef7a2e0e5705035491e7--