Re: Error in DatabaseMetaData TableColumn lenght.dec

From: Kris Jurka <books(at)ejurka(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Dario V(dot) Fassi" <software(at)sistemat(dot)com(dot)ar>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Error in DatabaseMetaData TableColumn lenght.dec
Date: 2004-07-11 05:13:14
Message-ID: Pine.BSO.4.56.0407110011060.24102@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Sat, 10 Jul 2004, Tom Lane wrote:

> Kris Jurka <books(at)ejurka(dot)com> writes:
> > 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.
>
> That doesn't sound like a usable answer at all. A client that believes
> this result will think that the value cannot contain any digits to the
> left of the decimal point --- which is certainly not so.

I blew this one. For some reason I was thinking 1000, 1000 was 1000 to
the left and right of the decimal.

> Does the JDBC spec allow you to return NULL for these entries? That's
> what we recently fixed the information_schema views to do for
> unconstrained numeric columns.

No, the method returns "int" which is a primitive type and therefore can't
be null. Maybe -1? I'm not sure what the best answer is.

Kris Jurka

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2004-07-11 13:27:46 Re: Timestamp Question
Previous Message Dario V. Fassi 2004-07-10 17:25:21 Re: Error in DatabaseMetaData TableColumn lenght.dec information