Removal of JDBC-ODBC Bridge from Java 8, what's next?

[Jay Orsaw]

https://blogs.oracle.com/Lance/entry/removal_of_the_jdbc_odbc


The article states

I would recommend that you use a JDBC driver provided by the vendor of your database or a commercial JDBC Driver instead of the JDBC-ODBC Bridge.

http://dev.mysql.com/downloads/connector/j/5.0.html I'll have to see if these Drivers work with 8.


Does anyone have any extra input?

[Bear Bibeault]

I updated the subject to be a tad more accurate.

As the blog post says, it's old and creaky and unsupported. I'm not sure I see the problem.

[Ulf Dittmer]

Agree with Bear. Any serious DB work should have moved away from the bridge 10 years ago.

[Paul Clapham]

And since Java 5, the JDK has shipped along with a database -- Java DB, a version of the Apache Derby database. This makes a half-baked ODBC interface even less useful.

[Jay Orsaw]

Just wanted to throw a heads up is all.... since this is the "what's new in Java 8" section.

Netbeans has it's own DB section which is what I personally have used.

[Cay Horstmann]

Now that's one of the things I did not write about in my book, in the interest of not boring the reader with inessential information

I did't imagine that anyone still uses the JDBC-ODBC bridge. For what? To talk to Microsoft Access??? If you do, I feel for you, but there are JDBC drivers for Access.

Cheers,

Cay

[Jeanne Boyarsky]

Cay Horstmann wrote:I did't imagine that anyone still uses the JDBC-ODBC bridge. For what? To talk to Microsoft Access??? If you do, I feel for you, but there are JDBC drivers for Access.

I bet in a year or so we get posters in the jDBC forum all panicked that they upgraded to Java 8 (not so early adopters) and their JDBC code to MS Access no longer works! Egads!