I'm going through the H2 source code for FunctionTable.java, and the first thing that I have a detailed question about is: is there some way to have H2's query optimizer supply me with an appropriate WHERE clause when such a clause can be determined to be constant?
That is, in the case of a multi-join scenario, I might be joining three "tables" (services, FunctionTables) and might also be using a WHERE clause that would help me filter down the values to be returned from, say, "table" 1. I understand (I think?) that the joining must be completed in memory, so all results to be joined must be supplied by the table function. But it seems to me that if the where clause involved a constant comparison (e.g. "WHERE t1.age > 20"), then it would be GREAT if I could somehow get access to that (parsed) where clause at the time that I am returning my table function's result set. I could avoid having to send back values that I know are redundant. I am no database internals expert so perhaps this is crashing into some edge case somewhere, or I'm simply not thinking clearly about the repercussions. Thanks, Laird -- 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.
