Our test passes for now so it's not critical. I'll keep an eye on it and if we see it again I'll report back here.
If you wanted to track it down though I'll try to help out. Not sure what you mean by thinking it's an issue processing the statement. That test has 2 assertions pertaining to the ResultSet prior to this first next() call that failed. I also debugged into the ResultSet calls and it showed no results. I stopped and updated the driver version before I tried troubleshooting any further. -- Sent from my Palm Pre [email protected] http://hibernate.orgOn May 9, 2010 12:59 PM, Thomas Mueller <[email protected]> wrote: Hi, I really don't know what the reason could have been. But most likely it's not a bug in the ResultSet implementation, but when processing the query. Tell me if you are still interested to find out what it was. 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. -- 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.
