Hi, The WHERE clause of a query seems to be polluting subqueries. >
I wouldn't call it 'pollute'. It's an optimization (certain statements are faster because of it). The WHERE of the outer select is being pushed into the subquery (query > optimizer?), but because the subquery depend on all its selected rows rows > for correct @variable calculations, moving the outer WHERE inside changes > the results. Is this intended behavior, or a bug? > It is intended behavior. Depending on the optimization, not all rows are processed. Maybe it is easier to create a Java function that returns a result set, and use it like a 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.
