Details
Description
Restricted Table Function support should pass NOT EQUAL restrictions to initScan. Currently any "!=" or "<>" constraints on the SQL used in the WHERE clause of a SELECT on a Restricted Table Funtion are not passed to the initScan method. These can be useful depending on how the Restricted Table Function is implemented.
Attachments
Attachments
Issue Links
- incorporates
-
DERBY-5372 Need to document that the != and <> operators are pushed into Restricted table functions (once the work on DERBY-5369 wraps up)
- Closed