Hi, I think I know what the problem is, but I'm not completely sure. I recently found and fixed a bug that could cause the problem you get:
"Version 1.3: when re-running the same query so that the previous result was re-used, and if the result set was large so that it was stored externally (in a temp file or in a temp table), then reading rows from both result sets resulted in an exception or wrong behavior." The problem was that the external result was shared. Is it possible that the distinct query returned many rows, so that the result was stored in a temp table? 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.
