[
https://issues.jboss.org/browse/TEIIDDES-992?page=com.atlassian.jira.plug...
]
Barry LaFond edited comment on TEIIDDES-992 at 7/13/11 12:29 PM:
-----------------------------------------------------------------
To Summarize:
We're talking about working with standard relational model "procedures" and
turning them into "functions" using the "FUNCTION = TRUE", adding a
couple of extension properties (Category and non-deterministic), and some validation to
make sure the params/results structure is ok AND tweaking our Indexing of these objects.
Basically the "Function Procudure" can only have input params and one output
param (i.e. no Result Set)
Create a "Create Pushdown Function" action when selecting a Relational Model
which provides a dialog that allows adding input params and defining the output param plus
create the new Procedure and set the FUNCTION = TRUE also as well as set the extension
properties
was (Author: blafond):
To Summarize:
We're talking about working with standard relational model "procedures" and
turning them into "functions" using the "FUNCTION = TRUE", adding a
couple of extension properties (Category and non-deterministic), and some validation to
make sure the params/results structure is ok AND tweaking our Indexing of these objects.
Basically the "Function Procudure" can only have input params and one output
param (i.e. no Result Set)
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
Affects Versions: 7.4
Reporter: Bernd Groh
Assignee: Barry LaFond
Fix For: 7.4
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:
http://www.atlassian.com/software/jira