Just occurred to me...
If someone needs some sort of flagging for features not supported in JDBC1
because they want to ensure portability or something we can still produce the
JDBC1 driver but allowing Java 1.2 code to be used in it. Or add some flagger
facility.
Regards to all,
Fernando
Fernando Nasser wrote:> Folks,
>
> We can't even get hold of a 1.1 JDK anymore. And it is preventing us
> from using the most basic stuff in the jdbc1 classes because they were
> introduced in 1.2.
>
> I am proposing we drop support for Java SDK 1.1 and JDBC1 altogether and
> keep only JDBC2 (for SDK 1.2 and SDK 1.3) and JDBC3 (for SDK 1.4).
>
> Concerns?
>
>
> P.S.: I even think support for 1.2 is not necessary. Does anyone know
> of a place where Java 1.2 is still being used? They must have a Java
> that old and still have a reasonably recent backend as the driver only
> support the last two previous versions (will be 7.2+ in the 7.4 release).
>
>
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
