need to call lockMeta before we synchronize on the Database object or
we get an ABBA deadlock

TestClearReferences currently fails because the fields in
LocalDateTimeUtils are not final.

found by running TestRandomSQL for long periods of time

Added new BITGET function, that returns true if and only if a specified bit in a long is set. This helps simulate bit fields in H2, which is an approach I'm using to significantly shrink database size.

reported by Alexander (vraimax2016)

since it breaks all the tests.

this reverts commit 37641c9a

Add support for Java 8 Date and Time API AKA JSR-310. On the face of it
the existing JDBC types java.sql.Date, java.sql.Time and
java.sql.Timestamp offer conversion methods to and from JSR-310 data
types. Unfortunately java.sql.Timestamp does silent data truncation
when the timestamp falls into a DST transition on the JVM time zone.
Worse still for java.time.OffsetDateTime there is no corresponding JDBC
type. Therefore these conversions have to be implemented. All of this
has to be programmed using reflection so the code compiles and can be
executed on Java 7.

Fix bug in picking the right index for INSERT..ON DUPLICATE KEY UPDATE when there are both UNIQUE and PRIMARY KEY constraints.

Since we now require at least Java 6 we can remove the Java 6 backwards
compatibility layer.

The current implementation of getObject does not support byte[]. This
is an issue for some people [1].

 [1] https://groups.google.com/forum/#!topic/h2-database/InWprFw2B0o

Some of the existing JDBC code is missing guards around debug
statements that allocate strings.