The good old "free as in beer" OSS consumer attitude :-) But let's not get mad about this. Let me try to answer those questions:
Do you know > (a) what the most common string representation of such a datatype is > There are two candidates. ISO 8601 compliant or SQL standard compliant. The latter can be seen here: http://www.andrew.cmu.edu/user/shadow/sql/sql1992.txt <timestamp literal> ::= TIMESTAMP <timestamp string> <timestamp string> ::= <quote> <date value> <space> <time value> [ <time zone interval> ] <quote> <date value> ::= <years value> <minus sign> <months value> <minus sign> <days value> <time value> ::= <hours value> <colon> <minutes value> <colon> <seconds value> <time zone interval> ::= <sign> <hours value> <colon> <minutes value> For improved SQL compatibility, I suggest supporting the latter and optionally supporting ISO 8601 (through explicit functions) > (b) how it is returned in a ResultSet, since there is no JDBC datatype for > it > This, unfortunately, is a complete mess :-) Most people probably bypass the Timestamp type and use Strings for deserialisation... > (c) how it is passed into a PreparedStatement ... and for serialisation. However, I don't think that too many people have thought about these things well enough. Most people just try to avoid this issue by normalising everything to UTC and deferring timezone calculations as long as possible, e.g. until displaying a date to the UI. Or they're lucky enough and their software only runs in a single timezone, when they can just get away with defaults in 98% of the time. In any case, I don't think you will be able to expect a quick answer from your users. This is a tough topic. Cheers Lukas Am Dienstag, 6. Mai 2014 10:40:40 UTC+2 schrieb Noel Grandin: > > > > On 2014-05-06 09:03, Lukas Eder wrote: > > > > And while we're at it, to make things more interesting, have you ever > considered supporting both the SQL standard > > TIMESTAMP WITHOUT TIMEZONE (your current implementation) and TIMESTAMP > WITH TIMEZONE data types? :-) > > > > I offered to implement it here: > > https://groups.google.com/d/msg/h2-database/rLakVH-CDXo/FL9bE_38_W0J > > But since nobody seemed willing to answer even basic questions about the > feature, nothing happened. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
