Just an FYI, I had to fix a bug recently to support a JDK6 version of JDBC.
I believe it was Oracle JDBC.
On Thu, Aug 16, 2018 at 3:06 AM, Sanne Grinovero
wrote:
> Hi Steve,
>
> thanks for confirming all that.
>
> There's of course some risk that future JDBC drivers will break
> things, but ther
Hi Steve,
thanks for confirming all that.
There's of course some risk that future JDBC drivers will break
things, but there's no breaking change in any version 9,10,11,12 ; I
believe it's unlikely and even if there's need for working around a
breaking change, we could evaluate various options. We
(Blob | Clob | NClob)Proxy are intended to do exactly what you said which
is exactly what the comment says. They were developed when we still
base-lined on Java 4 or 5. Java 6 added NClob and IIRC added methods to
Blob and Clob.
Hopefully if they add methods moving forward, they simply use defau
I'm trying to understand if we could remove some of the usages of
`java.lang.reflect.Proxy`.
Clearly it's a long journey and maybe we will never be able to remove
them all, but I would at least want to try avoiding most of their neet
at runtime - limiting their usage at bootstrap/configuration or
