As a result of our discussion I have raised these feature requests (as "improvements"):
https://issues.apache.org/jira/browse/DERBY-6117 => Pass more context information from Derby to Table Functions: e.g. Original SQL; Name of function that was called, User Info; Richer predicate expressions, Query plan https://issues.apache.org/jira/browse/DERBY-6118 => Allow Table Functions to return dynamic table shapes (e.g. specified using: "DYNAMIC RESULT SET" notation) Other related issues (including yours from above): https://issues.apache.org/jira/browse/DERBY-6036 https://issues.apache.org/jira/browse/DERBY-6109 https://issues.apache.org/jira/browse/DERBY-6115 Regards David -- View this message in context: http://apache-database.10148.n7.nabble.com/Limitations-of-Table-Functions-vs-old-VTIs-tp127988p128275.html Sent from the Apache Derby Developers mailing list archive at Nabble.com.
