| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Barry Lind <blind(at)xythos(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: PGResultSetMetaData |
| Date: | 2005-01-24 19:35:54 |
| Message-ID: | 41F54E1A.1050609@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-01-24 19:40:39 | Re: context classloader |
| Previous Message | Jean-Pierre Pelletier | 2005-01-24 18:30:40 | setObject on PGInterval throws "Unknown Type null" |