> IMHO, it is better to update BaseX documentation, and recommend to copy JDBC *.jar files to the ~\basex\lib\custom\ directory.
This way JDBC drivers will survive BaseX updates in-place.
Done; thank you.
Hello,
Congrats on the BaseX 12.2 release!
It seems that I bumped into a minor issue on a machine with MS Windows OS.
My XQuery is using SQL module, and for that I am using Microsoft JDBC Driver for SQL Server.
In particular, its mssql-jdbc-13.2.1.jre11.jar file needs to be in the ~basex\lib directory.
It looks like that in-place update from the BaseX 12.1 to BaseX 12.2 deleted
the ~basex\lib\mssql-jdbc-13.2.1.jre11.jar file.
I received an error message.
The solution was very simple, I copied the missing mssql-jdbc-13.2.1.jre11.jar file to the same location, restarted the BaseX GUI, and database calls started to work again.
As a test, I deleted Microsoft jar in the ~\basex\lib\
and copied it to the ~\basex\lib\custom\
And database calls started to work again.
The documentation says the following:
"..If you work with the full distributions of BaseX, you can copy the driver into the lib directory..."
https://docs.basex.org/main/SQL_Functions
IMHO, it is better to update BaseX documentation, and recommend to copy JDBC *.jar files to the ~\basex\lib\custom\ directory.
This way JDBC drivers will survive BaseX updates in-place.
Regards,
Yitzhak Khabinsky