to make it more obvious

Updated commercial support information

Use System.nanoTime() to check timeouts

System.currentTimeMillis() is influenced by system time corrections
whereas System.nanoTime() is strongly sequential. So it is better to use
System.nanoTime() when checking for timeouts and elapsed time.

Fix JDBC type of TIMESTAMP WITH TIME ZONE

* Added WITH to CREATE SCHEMA to supply default TableEngine params

* Updated docs to reflect changes in CREATE SCHEMA

* Review fixes - docs; code de-duplication; test for table engine params in schema

* Setter for table engine params in Schema

Optimized column vs constant comparisons

Currently the JDBC type of TIMESTAMP WITH TIME ZONE is Types.OTHER.
JDBC 4.2 has a dedicated type for this Types.TIMESTAMP_WITH_TIMEZONE.

Unfortunately this type is only available in JDBC 4.2/Java 1.8 so I
hard code the constant value instead of the constant reference.

unfortunately I had to hit it with the big synchronization stick. I
could no simple way to rescue the current rather clever code.

This bug was reported by Anatolii K  in this message:
https://groups.google.com/d/msg/h2-database/rhSoRhzeZzk/gc-pNlSpEwAJ

Issue #434 - parse engine params in CREATE TABLE w/o engine specified