Hi Fred, System Logger makes it very easy to retrieve logs without having to resort to third-party libraries. It's true that this is after Java 8, but I see that a Java 11 version is available in the hsqldb driver pack. Using one interface and two different implementations makes it very easy to support logging before and after Java 9.
Hi all, Java 9 offers the java.lang.System.Logger https://docs.oracle.com/javase/9/docs/api/java/lang/System.Logger.html logging facade, which provides easy access to logging for applications that load the HsqlDB JDBC driver. Does HsqlDB use this facade, and if not, are there any plans to do so? Thanks, Pierre
Hi Fred, Thank you for taking care of this issue. For me, it's no longer a problem since I can easily patch the ResultSets using javax.sql.rowset.CachedRowSet. That's what I'm doing, in fact. But it's true that it might be preferable to correct it to comply with the JDBC specification.
DatabaseMetaData.getTablePrivileges dont follow JDBC
Thank you Fred.
I am trying to integrate HsqlDB into Trino with the creation of a new HsqlDB connector. Perhaps it is possible to know the version of the JDBC client (it seems that the server version can be obtained by DatabaseMetaData.getDriverVersion()) in order to be able to write a test verifying that the server and the JDBC client are of the same version?
I am trying to integrate HsqlDB into Trino with the creation of a new HsqlDB connector. Is it possible to know the version of the JDBC client (the server version can be obtained by DatabaseMetaData.getDriverVersion()) so that I can write a test verifying that the server and the JDBC client are of the same version?
You are right Fred, I had the server in 2.7.2 and the client 2.7.3. If I test under 2.7.3 then the message disappears... Bravo for identifying this problem so quickly and sorry for the inconvenience...