Driver jdbc 3.0

If you need to use an older Java runtime, see the Java and JDBC specification support matrix to see if there's a supported driver version you can use. We're continually improving Java connectivity support. When you download the driver, there are multiple JAR files.

The name of the JAR file indicates the version of Java that it supports. If you are accessing this page from a non-English language version, and want to see the most up-to-date content, please select Read in English at the top of this page. You can download different languages from the US-English version site by selecting available languages.

We have also made changes with a stricter interpretation of the JDBC requirements, and removed some parts that were either obsolete or not functioning correctly. We recommend that you do not consider Jaybird 3. Test your application with Jaybird 3. Basic Java 9 compatibility is provided through the Java 8 version of the driver. See Jaybird 3.

Jaybird 2. All released versions are available at GitHub. Contact Us Site Map. Server Packages. After this update is applied, access to the master database is not required. The getSchemas method will work in SQL Azure and will work if there are collation differences between the master database and other databases. A supported hotfix is available from Microsoft.

However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. Oracle JDBC provides two different savepoint interfaces: one java. Savepoint for JDK1.

OracleSavepoint that works across all supported JDK versions. Connection; the Oracle JDK version-independent interface oracle. OracleConnection provides equivalent functionality. You create a savepoint using either Connection. Savepoint instance, or OracleConnection.

OracleSavepoint instance. A savepoint is either named or unnamed. You specify a savepoint's name by supplying a string to the setSavepoint method; if you do not specify a name, the savepoint is assigned an integer ID. Attempting to retrieve a name from an unnamed savepoint or attempting to retrieve an ID from a named savepoint throws an SQLException.

You roll back to a savepoint using Connection. If you try to roll back to a savepoint that has been released, SQLException is thrown. You remove a savepoint using Connection. As of Release 2 9.