sylvainlaurent / jdbc-performance-logger Goto Github PK

partially implemented
TODO :

• fix line feeds
• export batched statements too
• keep time-related columns together

Currently the limit of statements is 20'000. In some case we want to increase this threshold.
Maybe it will be a good idea to create a menu where we can set king of parameters

in situations where the underlying JDBC driver is not in the JVM classpath, the DriverManager cannot discover it through META-INF/services mechanism.
We should allow to specify the class name of the wrapped driver so that the WrappingDriver can get the JDBC connection.

If the driver is setup on several test servers, it would be nice to have the console connect to them and save the host/port to avoid typing it again

see http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html#JDBC_interceptors

fixed

only occur when the user sort by clicking on the TIMESTAMP column

The console cannot deserialize custom SQLException if the exception class is not in its classpath (e.g. HsqlException).

Statement.execute() then Statement.getResultSet() should be considered equivalent to executeQuery() (to record the number of rows fetched).

Besides, getMoreResults() is currently ignored, we need to support multiple resultsets

New feature : add a column that displays the delta of time of each statement compared to a specific statement. This allows to have a running sum of time spent in the DB...

Maybe 2 columns : one for the delta of absolute time, one for the running sum of time spent ?

There are new methods like Statement.executeLargeUpdate() in java 8.
Though they will work with the current version of the WrappingDriver, they will not appear in the console until they are taken into account by the proxy handler

Actually there won't be any ClassNotFoundException if @nonnull annotations are not in the classpath

currently only filtering is possible. it would be nice to highlight the statements that match the criteria entered on top.