FAQ

  1. Why use JDBC Logger in the first place?
  2. Why do we need JDBC Logger ? don't we already have P6Spy as a mature and feature full logging system?
  3. How does it work?
  4. What drivers does JDBC Logger work with?
Why use JDBC Logger in the first place?

Well the main reason is because JDBC drivers (or most of them at least) don't support logging out of performance concerns, and frameworks like Hibernate for example use prepared statements allot but have no support for properly logging them. With JDBC Logger we want you to be able to see in clear the full statement, not just a bunch of question marks.

[top]
Why do we need JDBC Logger ? don't we already have P6Spy as a mature and feature full logging system?

There are a couple of reasons why JDBC Logger is a great alternative to P6Spy. The main one would be that P6Spy is no longer maintained. The last release was back in 2003 and since that there has been very little development, and especially, bug fixing. And the second reason is that JDBC Logger is simpler to use, requiring as little configuration as possible, and very lightweight.

[top]
How does it work?

JDBC Logger is made out of a series of wrapper classes that just log every call and delegate to an actual JDBC driver.

[top]
What drivers does JDBC Logger work with?

We have a generic wrapper that should work fine with most JDBC drivers. Some drivers dough have extra features that are not present in the JDBC api so for those we have to implement custom wrappers. A list with drivers we've tested can be found on the Supported databases page.

[top]