Okay, that sounds absolutely reasonable, Timestamp alone sounds not powerful enough (and it has this strange pseudo-hierarchical relationship with Date).
Am Donnerstag, 26. Mai 2016 13:32:40 UTC+2 schrieb Noel Grandin: > > Hi > > At the moment, it looks like I'm going to have to change the > TimestampWithTimeZone datatype so that it no longer extends > javax.sql.Timestamp. > > So you'll need to extract it with > > (TimestampWithTimeZone) resultSet.getObject(i) > > It's going to be a standalone datatype with accessor methods for > year/month/day etc. > > The reason for this, is that in the presence of timezones, converting to > UTC time (which is necessary for > javax.sql.Timestamp) and back is inherently tricky, or at least it's > trickier than my brain can encompass. > > Of course, I'm open to better solutions: try uncommenting the code in > TestTimeStampWithTimeZone and then setting the > timezone to "Europe/Zurich" to see the failure mode. > > Regards, Noel. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
