Re: PGResultSetMetaData - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: PGResultSetMetaData
Date
Msg-id 41F54E1A.1050609@opencloud.com
Whole thread Raw
In response to Re: PGResultSetMetaData  ("Barry Lind" <blind@xythos.com>)
List pgsql-jdbc
Barry Lind wrote:
>
>>>(Kris, any reason why PGResultSetMetadata does not extend
>>>ResultSetMetadata?)
>
>
> By ResultSetMetadata I assume you mean java.sql.ResultSetMetadata.  The
> problem with having PGResultSetMetadata extend that interface is which
> one would you end up extending?  The JDBC1, JDBC2, JDBC3 or JDBC4
> version?

Whichever one you're building against.. they're all called
java.sql.ResultSetMetadata.

The reason I ask is that the current scheme is a little awkward to use
if you want to use both the standard and extra interface methods. Either
you need two variables providing different interface views on the same
object, or you do a lot of casting.

-O


pgsql-jdbc by date:

Previous
From: "Jean-Pierre Pelletier"
Date:
Subject: setObject on PGInterval throws "Unknown Type null"
Next
From: Oliver Jowett
Date:
Subject: Re: context classloader