Re: JDK 1.4 challenge, opinions please

On 17 Dec 2001 09:46:41 -0700, you wrote:
>Couldn't the method that creates the resultSet to be used/abused be an
>abstract method that the jdbcge2/DatabaseMetaData calls? For instance,
>jdbcge2/DatabaseMetaData has a protected method
> protected ResultSet getResultSet();
>and then the jdbc2/DatabaseMetaData and jdbc3/DatabaseMetaData classes
>that inherit from jdbcge2/DatabaseMetaData implement it to return the
>proper one? Then jdbcge2/DatabaseMetaData can set the needed data in
>the ResultSet.

Yes, this looks like a better idea. Its amazing how
non-intuitive Object Orientation can be :-) I'll continue on
this path.

>Did that make sense? ;-)

Very much so! Thanks for pointing me in the right direction.

And I wrote:
>> There are other problems up ahead though, such as common code in
>> jdbcge2 that references constants from java.sql (e.g.
>> FETCH_FORWARD).

This turns out to be a non-problem. I just needed to qualify the
constants with the java.sql.Interface prefix, since the class
containing this code no longer implements the interface.

There may be some cases of constants that exist only in some
versions of the JDBC API, but this can be handled with a similar
inheritance workaround as you described for creating
ResultSet's.

Regards,
René Pijlman <rene(at)lab(dot)applinet(dot)nl>