use the same name for the last_insert_id method name as the function 
name it calls ... also add a connection.last_insert_id naming convention
last_insert_id for Derby using (IDENTITY_VAL_LOCAL()) currently not used
DB2 supports standalone VALUES statements (just like Derby does)
refactor DB2's `last_insert_id` using IDENTITY_VAL_LOCAL()
as suspected "SELECT IDENTITY_VAL_LOCAL() FROM table" is non-sense
spec adapter's `execute` behavior and make sure it complies for DB2
Postgres (prep.stmnts) : `statement.setNull(index)` needs `Types.BINARY`
it's likely best to stick with JDBC 3 API for BLOBs (in case of older drivers)
[postgresql] handle infinite timestamps with prepared statements
recompile jar