Hi That doesn't make any sense - we convert java.sql.Timestamp to a ValueTimestamp object internally, and convert back when the user requests a value, so there is no way they could corrupt the data by writing to a Timestamp object.
-- Noel. Thomas Mueller wrote: > Hi, > > This is strange. The checksum of the btree index page is correct, > meaning it doesn't look like a corruption of the database file. But > the timestamp in the index doesn't match the timestamp in the table > itself: > > In the table: TIMESTAMP '2011-05-11 15:12:48.386' > in the index: TIMESTAMP '2011-05-11 15:12:48.-419306368' > > So there is a negative value for the timestamp nanoseconds. That's > very strange. But there are also some other strange timestamps, some > with nanoseconds, and dates 0-12-31 00:00:00.259, -2010-06-06 > 00:00:12.936, 1970-01-01 00:01:08.018. > > To me, it looks like the timestamp is overwritten somehow while > inserting the data. This might be possible because timestamps are > mutable (java.sql.Timestamp.setNanos, setTime). > > Do you re-use the same timestamp object in your application, and use > one of those methods to update it in a different thread? > > Regards, > Thomas > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
