bugfix: rounding error was causing days to shift during coercion, when the JVM is in a timezone ahead of GMT/UTC
Upgrade to optiq-0.4.15.
Now we've upgraded optiq, remove workaround for the fact that DATE and TIME literals were stored as a long, not int.
Match further changes to Optiq: API changes to Schema, Table and Context; change semantics of ResultSet.getXxx now shifts time, date, timestamp values to local time unless you pass a Calendar object to getTimestamp(int, Calendar) or similar.
Updated to be compatible with optiq-0.4.15