JDBC API based savepoint support (that should work for all adapters)
simplified set savepoint(s) tracking on the Ruby side
[mysql] use 'extended' savepoint support - we allow passing a name
explicit when current_ method supposed to return a new name + refactoring
emulate savepoint support for SQLite3's Ruby JDBC connection (Java API)
postgres - use provided JDBC API for savepoints but log savepoint SQL
sqlite3 - use provided JDBC API for savepoints but log savepoint SQL
release savepoint test + assert that MySQL supports savepoints
transaction tests for derby
passing H2 database transaction tests
hsqldb transaction tests
add a H2Module Java class although no (Ruby) methods implemented
pass the jdbc connection into adapter.init_connection
use init connection to check if connection_alive_sql needed (old driver)
init_connection JDBC 3 driver check - connection_alive_sql needed
refactor Derby's jar version check into init_connection
raise AR::ConnectionFailed instead of RuntimeError - "old" driver detected
make sure shutdown/startup overrides call super (Test::Unit::TestCase)
assert stdout expectations for rake tasks after teardown
Java API: prepared statements pass column into set (param) methods 
+ make'em protected