Description
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.
Attachments
Attachments
Issue Links
- incorporates
-
DERBY-3138 Optimizer error when vtis are invoked with correlated references to outer query blocks
- Closed
-
DERBY-3072 User documentation for Table Functions
- Closed
- is blocked by
-
DERBY-3135 TableFunctionTest fails with weme6.1 on trunk
- Closed
- is related to
-
DERBY-1651 Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.
- In Progress
-
DERBY-3129 Create Demo code, showing how to create and use table functions.
- Closed
- relates to
-
DERBY-3545 NullPointerException in TableFunctionTest.noSpecialCollation and specialCollation
- Closed
-
DERBY-3595 TableFunctionTest.SpecialCollation and NoSpecialCollation fail with IBM iseries in checkGetXXXCalls
- Closed
-
DERBY-3616 TableFunctionTest fails under Ubuntu 7.10
- Closed