Talk:Java Database Connectivity

NOT an acronym

JDBC does not stand for "Java Database Connectivity". This is a backronym. See http://java.sun.com/j2se/1.5.0/docs/guide/jdbc/getstart/intro.html#1018464, first paragraph. The main page should be titled JDBC, with Java Database Connectivity redirecting to it. --Nambio 00:11, 29 May 2006 (UTC)

And from the same site, http://java.sun.com/javase/technologies/database/. Sun seems to be contradicting itself for some reason. WP:NAME "[p]refer[s] spelled-out phrases to abbreviations", so even though JDBC is overwhelmingly more popular, the fact that Sun has referred to it as "Java Database Connectivity" mitigates against using the acronym as the page title (see ODBC as a parallel). --DeLarge 23:29, 25 March 2007 (UTC)

I heard it was a trademark issue. In some jurisdictions, you can't trademark an acronym so they had to make JDBC its name, not its acronym. (Northernhenge (talk) 22:37, 5 April 2008 (UTC))

Example is dated

Class.forName("some string"); is back from 1.0 days and while it still works for backwards compatiblity is not preferred. Jon 13:58, 30 March 2007 (UTC)

Type 5

Deleted section on "type 5". There is no clear definition of what a type 5 architecture is, unlike types 1-4. This is not officially terminology adopted through the JCP. It seems to be to be mostly an invention of Progress Software's marketing department.--SJK (talk) 10:51, 30 October 2010 (UTC)

Possible Original Research

===Bad Examples===

The Internet is full of wrong JDBC examples, even Oracle and the acquired SUN keep wrong examples where they clearly show they do not know Java has exceptions and resources must be closed in a finally clause.

What is the problem with referencing wrong examples? Do you mean every time I add a reference there is original research? —Preceding unsigned comment added by 87.218.251.115 (talk) 13:37, 7 April 2011 (UTC)

This statement appears to come from an analysis of the reference code, which is original research. While well-intentioned, I'm afraid that either this section should be either deleted or better references should be used. --Sbluen (talk) 06:17, 3 April 2011 (UTC)

Seconded, also i think this article reads far too much like a howto SmackEater (talk) 09:08, 4 April 2011 (UTC)

The closing of statements is recommended here. Properly releasing ressouces that were allocated previously is programming basics, no special citations needed here imho. Failure to do so leads to leaks. — Preceding unsigned comment added by 81.7.230.226 (talk) 17:45, 24 January 2013 (UTC)

References

Should extend connection pool examples

Now: "Examples of connection pools include BoneCP, C3P0 and DBCP" Should add https://github.com/brettwooldridge/HikariCP and maybe deprecate C3PO (and DBCP?), — Preceding unsigned comment added by 84.48.115.70 (talk) 12:04, 1 April 2015 (UTC)

Please please do NOT catch Throwable.

To an anonymous 194.176.105.142. While your link in diff 698792584 contains a moderately bad advice to catch a general Exception, which is only suitable for simplistic examples and not for production, catching Throwable is a huge mistake. Please read: http://stackoverflow.com/questions/2274102/difference-between-using-throwable-and-exception-in-a-try-catch — Preceding unsigned comment added by VictorSergienko (talk • contribs) 11:32, 21 September 2016 (UTC)

Please, see: http://stackoverflow.com/questions/34664936/should-i-catch-all-exceptions-or-just-sqlexception-when-closing-jdbc-resources-o and https://github.com/spring-projects/spring-framework/blob/master/spring-jdbc/src/main/java/org/springframework/jdbc/support/JdbcUtils.java Jsmithgeorge (talk) 19:36, 8 December 2016 (UTC)

Please note that a) the answer you refer to has 0 upvotes; b) it catches Exception, not Throwable; c) even that answer says "Just make sure to pass along everything you don't know how to handle (so the caller has to)". CAN you really handle OutOfMemoryError in your catch (Throwable)? InternalError? UnknownError? d) I don't even think that Spring code knows what it is doing. Looking forward to a better code example from you, which does handle these. DOES this example need to handle IllegalClassFormatException? I highly doubt. Please don't teach people to catch what they don't know how to handle. The rule is: you ONLY catch those that you know what to do with. A reference to Oracle docs: "This feature can reduce code duplication and lessen the temptation to catch an overly broad exception." VictorSergienko (talk) —Preceding undated comment added 17:51, 15 December 2016 (UTC)

Also read: Java API documentation: "An Error is a subclass of Throwable that indicates serious problems that a reasonable application should not try to catch." — Preceding unsigned comment added by VictorSergienko (talk • contribs) 18:13, 15 December 2016 (UTC)

Current JDBC Specification is JDBC 4.5 released 2026-04-10; JDBC 4.4 was released on 2025-03-11

I can spell Java (c.o.f.f.e.e), but: while tracking current versions of the JDBC specification, Google identified it as version 4.5 while showing this Wikipedia page which still says 4.3, released on 2017-09-17. Therefore, this page is due for some updating by one or more SMEs. I can't offer help with the updates; I'm not an SME wrt to Java or JDBC.

Google notes:

While Java SE 26 introduces the JDBC 4.5 spec definitions, many enterprise database drivers (such as those from Oracle and Microsoft) are engineered to be backward compatible. Most existing database infrastructures heavily rely on JDBC 4.3 or JDBC 4.2 features for standard query execution.

And you can find the specification at the JCP (Java Community Process) website under JSR-000221 JDBC API Specification 4.5 (Maintenance Release 5). Also, there’s way of finding JSRs (Java Specification Requests), and in particular the history of JSR221. That shows that JDBC 4.5 was released on 2026-04-10. JDBC 4.4 was released on 2025-03-11, JDBC 4.3 was released on 2017-09-17, JDBC 4.2 was released on 2014-03-04, JDBC 4.1 was released on 2011-10-13, and JDBC 4.0 was released on 2006-12-11. Babbling.Brook (talk) 17:16, 11 June 2026 (UTC)