Uploaded image for project: 'JDO'
  1. JDO
  2. JDO-771

Update requirement of ConnectionDriverName since JDBC 4 changed requirements

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: JDO 3.1
    • Fix Version/s: JDO 3.2
    • Component/s: api, specification
    • Labels:
      None

      Description

      JDBC 4.0 changed the requirement for specifying a JDBC driver name. Previously an application had to load the class to register the driver by use of Class.forName.
      All JDBC 4.0+ drivers should register themselves. See
      https://community.oracle.com/docs/DOC-983612

      This likely means that a JDO provider will not require the javax.jdo.option.ConnectionDriverName to be supplied.
      DataNucleus (v5.1.5+) certainly doesn't require it, and only previously used it for loading the driver as per previous JDBC semantics.

      This is only referred to in section 11.1 and Appendix G of the spec that I can see. Perhaps we can omit it in JDO 3.2+, particularly as the JRE in use will require JDBC v4+?

        Attachments

          Activity

            People

            • Assignee:
              clr Craig L Russell
              Reporter:
              andyj Andy Jefferson
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: