Tests for timestamps

since we no longer support jdk6

Improve TimestampWithTimeZone javadoc

I found the comments in TimestampWithTimeZone not helpful in
understanding the semantics of the public methods.

This commit includes the following changes

 - add comments to previously not commented public methods in
   TimestampWithTimeZone that describe the semantics
 - add more verifications to TestTimeStampWithTimeZone to make sure the
   actual behavior matches the documented behavior

Change getters in TimestampWithTimeZone to int

The convenience accessors getYear getMonth and getDay in
TimestampWithTimeZone return long even though their values fall within
the range of int. This makes them a bit inconvenient to work with as
most APIs (Calendar, LocalDateTime) take int for such values.

This commit contains the following changes

 - change TimestampWithTimeZone#getYear() to return an int instead of
   a long
 - change TimestampWithTimeZone#getMonth() to return an int instead of
   a long
 - change TimestampWithTimeZone#getDay() to return an int instead of
   a long

Added missing source encoding. Assuming UTF-8.

Add support for converting JAVA_OBJECT to UUID

Add support for getObject(int|String, Class)

Both JdbcResultSet and JdbcCallableStatement currently do not support
getObject(int, Class) and getObject(String, Class) but support is easy
to add.

This commits contains the following changes:

 - add support for getObject(int, Class) and getObject(String, Class)
    with the following types: BigDecimal, String, Boolean, Byte, Short,
   Integer, Long, Float, Double, Date, Time, Timestamp, UUID,
   TimestampWithTimeZone and Geometry subclasses
 - extend the existing getObject tests to cover these new methods

Most notably missing is support for LOBs and arrays including primitive
arrays but this can always be added later.

Server: use xdg-open to open the WebConsole in the user's preferred browser on Linux

Support for BEFORE and AFTER clauses when using multiple columns in A…

Synchronized on database when unlock tables

Respect format codes from Bind message when sending results

From https://www.postgresql.org/docs/9.1/static/protocol-message-formats.html:

  Bind (F)

  ...

  After the last parameter, the following fields appear:

  Int16

    The number of result-column format codes that follow (denoted R
    below). This can be zero to indicate that there are no result
    columns or that the result columns should all use the default
    format (text); or one, in which case the specified format code is
    applied to all result columns (if any); or it can equal the actual
    number of result columns of the query.

  Int16[R]

    The result-column format codes. Each must presently be zero (text)
    or one (binary).

Also fix testBinaryTypes test:

- force binary by setting prepareThreshold to -1
- handle REAL type as float

Without the fix the corrected test testBinaryTypes fails:

  05:25:02 21:55:02.666 org.h2.test.unit.TestPgServer Expected: 12345678 actual: 825373492
  Exception in thread "main" java.lang.AssertionError: Expected: 12345678 actual: 825373492
      at org.h2.test.TestBase.fail(TestBase.java:464)
      at org.h2.test.TestBase.assertEquals(TestBase.java:617)
      at org.h2.test.unit.TestPgServer.testBinaryTypes(TestPgServer.java:404)
      at org.h2.test.unit.TestPgServer.test(TestPgServer.java:51)
      at org.h2.test.unit.TestPgServer.main(TestPgServer.java:41)

To be in sync with Build.java

bug introduced with 29c9cc75 "Merge pull request #323 from
Akkuzin/regexp_match_enhance"

Prior to the fix the test would fail with NPE:

  Exception in thread "main" java.lang.NullPointerException
      at org.postgresql.jdbc2.AbstractJdbc2ResultSet.checkColumnIndex(AbstractJdbc2ResultSet.java:2619)
      at org.postgresql.jdbc2.AbstractJdbc2ResultSet.checkResultSet(AbstractJdbc2ResultSet.java:2637)
      at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getInt(AbstractJdbc2ResultSet.java:2005)
      at org.h2.test.server.TestPGServer.testPrepareWithUnspecifiedType(TestPGServer.java:76)
      at org.h2.test.server.TestPGServer.test(TestPGServer.java:44)
      at org.h2.test.server.TestPGServer.main(TestPGServer.java:29)

According to https://www.postgresql.org/docs/9.1/static/protocol-flow.html

  The Describe message (statement variant) specifies the name of an
  existing prepared statement (or an empty string for the unnamed
  prepared statement). The response is a ParameterDescription message
  describing the parameters needed by the statement, followed by a
  RowDescription message describing the rows that will be returned when
  the statement is eventually executed (or a NoData message if the
  statement will not return rows)

* translation console start

* translation continue

* translation continue

* translation console start

* translation continue

* translation continue

* translation correction

* translation correction

Fix document of return value of TIMESTAMPADD method