I submitted a query via jdbc to pull back rows in a given time period ordered by the time period in ascending order.
The resultset came back with 150 or rows but with the first 100 rows repetitions of a group of 8 rows for several iterations and then the remaining rows correctly. When the query is run in the web console it returns the same number of rows in the proper order with no duplicates. As further detail, I have an app that replicates the last 4 hours of data over a 10 day period using INSERT / SELECT to replicate the data but change the time-period of each row. It is this collection of rows that appear messed up. What I'm thinking is that H2 used a pointer to get the data from the source rows and not where they were actually copied in the database whereas the h2 console uses a different means to get the data and it is correctly returned. When doing INSERT via SELECT do I need to rebuild the index tables? I saw an earlier post where when using CREATE TABLE via SELECT you had to do that action. I'm using version 1.2.147 and plan to move to 1.2.164 to see if that fixes the problem. If its a known problem is it fixed in version 164. Thanks, Jim McArdle -- 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.
