log4jdbc / News: Recent posts

In this release, I've cleaned up the generated SQL a bit and added a bunch more options for controlling the SQL output. You can now turn on and off the type of SQL you want to log. For example, you might want to log only INSERT SQL statements and generate a SQL script from the logger output.

I also added an extra logger that shows whenever a new connection is opened, or a connection is closed. It also dumps all open connection numbers at each open and close event, so you can see how many connections your program uses as it progresses (great for detecting connections leaks!)... read more

The beta release proved to be quite stable-- I just added one minor fix in this release to make the pre-loading of well known JDBC drivers be a little more robust.

You can download log4jdbc from here:

http://sourceforge.net/project/showfiles.php?group_id=194500

Please don't hesitate to send questions, comments and suggestions to
Arthur Blake
arthur_blake at users.sourceforge.net

log4jdbc 1.1 beta 1 release.

Added HSQLDB (org.hsqldb.jdbcDriver) and H2 (org.h2.Driver) to list of "well known" drivers that log4jdbc looks for at startup.

New timing threshold option settings that makes it easier to find slower running SQL.
See http://log4jdbc.sourceforge.net/index.html#advanced for more information.
Special thanks to Lilianne E. Blaze for the idea and initial implementation.... read more

log4jdbc 1.1 now has JDBC 4.0 support!

JDBC 3 and JDBC 4 will both be fully supported going forward.

I've been testing the JDBC 4 support with Apache Derby (the only database that I know of that currently has JDBC 4 support) and it's working quite well.

The code base has been split into separate JDBC 3 and JDBC 4 versions.

While this causes some code to be duplicated, I ultimately decided to do it this way because it's much simpler than trying to detect which version to use at runtime (and results in smaller jar file sizes) and so that I can use the newer JDK 1.6 features in the JDBC 4 version going forward without having to worry about backporting, etc. for JDK 1.4.... read more

log4jdbc 1.1 now uses the simple logging facade for java (SLF4J) instead of log4j directly.

This means that you can now use a number of popular java logging frameworks with log4jdbc, rather than being confined only to log4j.

See http://www.slf4j.org for more information on SLF4J.

The 1.1 alpha 1 release of log4jdbc has fixed a few minor bugs in the 1.0 release. See the CHANGES file for all details at http://log4jdbc.sourceforge.net/CHANGES... read more

log4jdbc is a JDBC driver that can log SQL and/or JDBC calls (and optionally SQL timing information) for other JDBC drivers, using the log4j 1.2.x logging system.

This JDBC driver can be "dropped in" to log the SQL and JDBC calls of any java application without modifying the original application.

This project was started over 5 years ago, to scratch an "itch". I needed a way to quickly and transparently log the SQL that an application was generating in order to find where in the application code problematic SQL was being generated from. Often times application code that I was contracted to work on didn't have it's own sufficient exception handling and logging to figure out this information without a significant amount of digging.... read more