Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle JDBC metadata screwups

Re: Oracle JDBC metadata screwups

From: Volker Hetzer <volker.hetzer_at_ieee.org>
Date: Mon, 15 Dec 2003 20:33:29 +0100
Message-ID: <brl2aa$ca8$1@news.fujitsu-siemens.com>

"Joe Weinstein" <joeNOSPAM_at_bea.com> schrieb im Newsbeitrag news:3FDDFDD9.4010603_at_bea.com...
>
>
> Mike Schuler wrote:
>
> > Why are there so many problems with Oracle JDBC drivers - ever since
> > they came out? I can't differentiate between SYSTEM TABLES and TABLES,
> > the ResultSetMetaData doesn't have values for decimal places or sizes,
> > etc...
> > I'm using Oracle 9i, with the newest ojdbc14.jar and I can't believe
> > we're the only ones with these problems.
>
> It's not the driver's fault. The driver has to depend on what
> the DBMS sends, especially for result set metadata etc. It
> would take a (probably not backward-compatible) change to the
> DBMS protocol for it to start returning more/better metadata.
> As an example, the metadata is insuffient, for most numerical
> data, for the driver to adhere to the JDBC spec for what object
> to make for getObject(). That's why the driver punts on this
> issue, and just returns a BigDecimal for all numeric data.
But when using C/ESQL one can get at the column type/precision. One just has to ask the output descriptor.

Greetings!
Volker Received on Mon Dec 15 2003 - 13:33:29 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US