Recent changes to patches

SQL batch file logger

Kosta — Tue, 27 Jun 2006 21:44:21 -0000

Appender that writes a trace of JDBC activity into an
SQL batch file that can be later "replayed" using a
generic SQL client.

Usage:

- compile BatchFileLogger.java with p6spy.jar in
classpath or copy it into
com/p6spy/engine/logging/appender subdirectory of the
project's source and make the project

- modify the spy.properties file to make p6spy use
this appender by adding line

appender=com.p6spy.engine.logging.appender.BatchFileLo
gger

and commenting out the existing appender

#appender=com.p6spy.engine.logging.appender.FileLogger

- specify an alternative log file name in
spy.properties so that diagnostic entries to spy.log
made by p6spy at startup do not mess up your batch.
Here's how it works for me:

logfile = spy.sql

The appender writes the text of SQL statements as
well as commit and rollback commands to the specified
file, each on a new line. For prepared statements the
effective text resulting from substitution of
parameter signs with their values is written. Other
event categories are logged as SQL comments ("-- "
followed by the category name). Exceptions and text
are silently discarded. All SQL statements except the
last one will have a delimiter character ';' appended
to them.

This batch format works well with WinSQL. The format
is hardcoded, so if you want to make it configurable
you'll have to patch my patch or write your own :)

Enjoy!

JDBC Leak Detecter

Michael Harhen — Sun, 27 Feb 2005 23:06:00 -0000

Detects JDBC memory leaks - i.e. Connections,
Statements, and ResultSets that have not been closed.

Uses a new P6Spy module - simple to use.

Exclude resultset log

Diego Espada — Thu, 24 Feb 2005 12:58:44 -0000

p6spy 1.3 always logs the resultset log category.
Install this patch in the package
com.p6spy.engine.common and write "resultset" in the
excludecategories parameter of the spy.properties file
to get this working.

DateFormat patch

Anonymous — Thu, 29 May 2003 21:24:31 -0000

The date format used in the Prepared statement
was toString on the date/time object.
this would cause problem if we try to reexcecute
query against database( db expects a date format)
from the log.

to fix this i have added a new property called
databasdialectdateformat in spy.properties.
and changed classes P6SpyOptions.java
and P6PreparedStatement.java to pick up this
date format and insert date in this format in the
queries.

pls. find the attached dateformat.jar
for the new source code.