I believe oracle.jdbc.V8Compatible is deprecated in Oracle 11
This is because for the DATE column, Oracle now does what it did before 8i, for example. to return java.sql.Timestamp instance for DATE column?
Their FAQ covers:
http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-faq-090281.html#08_00
Oracle JDBC 11.1 fixes this problem. Starting with this version, the driver maps SQL DATE columns to java.sql.Timestamp by default. There is no need to install V8Compatible to get the correct display. V8Compatible is strongly discouraged. You should not use it at all. Setting it to true will not hurt anything, but you should stop using it.
As mentioned above, 11.1 drivers by default convert SQL DATE to Timestamp when reading from the database. This has always been the right thing, and changing 9i was a mistake. 11.1 drivers returned to the correct behavior.
Source: https://habr.com/ru/post/1334523/More articles:How to get hierarchical data using Linq-to-entity? - c #Is there an Apache Shinding port, a version of Java that works in the Google App Engine? - javaProfiling Silverlight 4 - profilerFull definition of a full copy of SQL Server - sql-serverRead / write sockets ("full-duplex") at the same time on Linux (aio specifically) - linuxMy C ++ executable works faster outside of Visual Studio 2008 than inside, even in the release - c ++Visual Studio Notebook Application - debuggingIs it possible to throw an exception - c #Google video site - pythonProblems with Nhibernate and linq - linqAll Articles