![]() ![]() If there are new objects introduced in 12.2 then an older driver will NOT have Java equivalents for those objects. There are a limited number of features/functionality new to 12.2 that might require the 1.8 jar file but unless your app or test harness is using those 12.2 features just continue to use the JDBC jar file you always used.Īn older jar file will NOT have functionality to deal SPECIFICALLY with functionality that is new to 12.2. What I told you in your other thread still applies: Your external app can use any JDBC jar that supports the version of the DB you are using. ![]() The ONLY caveat with ANY client tool you use is that you can NOT use features that exist in the DB if support for them doesn't exist in the client. They might use an OCI (thick) client such as the full Oracle client suite, the Oracle Instant client, Oracle's JDBC jar file or even a combination of the above (JDBC jar with OCI thick support). The ONLY thing those tools have in common is that they GENERALLY (but not always) use an Oracle component in their client to talk to establish and use the connection to the database. ![]() They connect to it with Java, C, C++, ODBC and other client tools. Millions of people all over the world use it. a Java stored procedure) then you will be using the version of Java that is built into the DB (NOT any external version. You need to separate the Oracle database from the Java (and ANY jars, including JDBC) you use externallyĮxcept for the JDBC jar file you use Oracle does NOT know, and does not care, what version of Java you use outside the database. The main question we needed answered is that if we used the ojdbc6.jar from the Oracle 12.1.0 release and were running our application against Java 8, would this be supported?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |