]
Steven Hawkins commented on TEIIDDES-992:
-----------------------------------------
With Bernd's clarification there is still room for improvement from a design time
perspective. Something we've talked about before is that functions have been
arbitrarily separated from the relational metamodel. If functions were part of model tied
to the source, there's no reason why the runtime couldn't treat them as pushdown
functions. If we still maintain the separation between the metamodels (since I'm
assuming that merging them would be too much work) you could just add model to source
assignment logic for function models in the same way that is done for physical models. It
wouldn't even be necessary to distinguish between physical/virtual function models,
since the function metadata itself declares whether it's for pushdown or not. You
would just want to make the source assignment of a function model optional.
Allow the use of pushdown functions without requiring Java
programming
----------------------------------------------------------------------
Key: TEIIDDES-992
URL:
https://issues.jboss.org/browse/TEIIDDES-992
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Bernd Groh
Currently, in order to use a database function, even if pushdown is required, it is still
necessary to add the function interface to a Java class within the connector, and the
connector then must be deployed to the server in order to allow for this pushdown function
to be used within the Designer. This creates a lot of extra effort every time you want to
make use of a new database function. Particularly, given the schema designer doesn't
necessarily have access to either the connector code or the server, and then must involve
other parties simply to be able to use an additional database function. It would be very
beneficial to speedy schema development if that was not necessary, and if, say, the
interface could be defined on the Designer side, added to the VDB, and then deployed as
part of the VDB.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: