Re: Error in DatabaseMetaData TableColumn lenght.dec information

From: "Dario V(dot) Fassi" <software(at)sistemat(dot)com(dot)ar>
To: Kris Jurka <books(at)ejurka(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Error in DatabaseMetaData TableColumn lenght.dec information
Date: 2004-07-10 17:25:21
Message-ID: 40F02681.2010209@sistemat.com.ar
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Kris Jurka wrote:

>On Fri, 2 Jul 2004, Dario V. Fassi wrote:
>
>
>
>>Hi, I whish to report a erroneous information returned by
>>DatabaseMetaData.getColumns() method.
>>
>>Suppose
>>
>>CREATE TABLE A ( f1 DEC(6,3), f2 dec(6,3) );
>>CREATE VIEW B as ( select ( f1 + f2 ) as f from a;
>>
>>Then DatabaseMetaData.getColumns() returns:
>>
>>VIEW B
>> F NUMERIC( 65535 , -65531 )
>>
>>
>>
>
>I've modified the cvs version of the driver to return numeric(1000,1000)
>which is the maximum precision and scale you are allowed to define. A
>more complete solution is outside the realm of the JDBC driver.
>
>Kris Jurka
>
>
Kris,

A return value of numeric(1000,1000) , is far better than
numeric(65535,-65531) , but this mean a number with all the presicion in
the fractional part and is not very usefull.

Why not a more login value like "Numeric(100,50)" , yet oversized
but more appropiate.
Can you imagine a number with 1000 digit's presicion, it's impractical
and undisplayable.

Dario Fassi.

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2004-07-11 05:13:14 Re: Error in DatabaseMetaData TableColumn lenght.dec
Previous Message Dario V. Fassi 2004-07-10 17:20:22 Re: Timestamp Question