[ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511568 ]
Daniel John Debrunner commented on DERBY-716: --------------------------------------------- I see that isRowMultiSet is used to indicate the function is a table function. Would it not be clearer to have an explict state in RoutineAliasInfo that the function is a table function, rather than overloading the return type to indicate this? Also look at DERBY-2917, I'm trying to separate TypeDescriptor & DataTypeDescriptor, thus the cast you didn't want to add won't be valid soon. > Re-enable VTIs > -------------- > > Key: DERBY-716 > URL: https://issues.apache.org/jira/browse/DERBY-716 > Project: Derby > Issue Type: New Feature > Components: SQL > Reporter: Rick Hillegas > Assignee: Rick Hillegas > Attachments: derby-716-01-basic-aa.diff, functionTables.html, > functionTables.html, functionTables.html > > > Cloudscape used to expose Virtual Table Interfaces, by which any class which > implemented ResultSet could be included in a query's FROM list. Derby still > exposes a number of these VTIs as diagnostic tools. However, Derby now > prevents customers from declaring their own VTIs. The parser raises an error > if a VTI's package isn't one of the Derby diagnostic packages. > This is a very powerful feature which customers can use to solve many > problems. We should discuss the reasons that it was disabled and come up with > a plan for putting this power back into our customers' hands. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.