I am part of the development team developing the database tool DbVisualizer.
DbVisualizer is general database tool allowing connection to a vast number of databases/data sources.
DbVisualizer does use java.util.logging as its logging mechanism.
While testing with your jdbc driver (org.mongodb:mongodb-jdbc) we have noticed that the driver disables all our loggers.
This without using/specifying any driver properties.
From a general point of view, I would expect logging configuration to be performed on an application level and not on a JDBC driver level. E.g having multiple live connections using drivers from multiple vendors would easily result in undefined logging.
My suggestion is:
If logging related driver properties are not specified (E.g. loglevel) don't do anything regarding java.util.logging
If loglevel is specified make sure not to affect any existing handlers/loggers
Hi!
I am part of the development team developing the database tool DbVisualizer. DbVisualizer is general database tool allowing connection to a vast number of databases/data sources. DbVisualizer does use java.util.logging as its logging mechanism. While testing with your jdbc driver (org.mongodb:mongodb-jdbc) we have noticed that the driver disables all our loggers. This without using/specifying any driver properties.
From a general point of view, I would expect logging configuration to be performed on an application level and not on a JDBC driver level. E.g having multiple live connections using drivers from multiple vendors would easily result in undefined logging.
My suggestion is:
Kind Regards Ulf