[ https://issues.jboss.org/browse/TEIIDDES-1309?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1309: ---------------------------------------- In 8.0 we could actually keep the Function Metamodel but prevent the Functions from being registered and used in Transformations. This will allow for fully EMF-aware mapping of Function model EObjects to comparable relational procedure EObjects. Would also allow for robust migration utilities. Scenario is an old FunctionDefinition.xmi file contains convertCurrency() method which is used in one or more SQL Transformations. STEP 1: Convert FunctionDefinition.xmi ScalarFunctions to relational Procedures and specify new or existing relational model (push-down functions) as well as allowing creating View model procedures (user defined functions). The act of creating new "procedures" will force them to be registered and ready for use in SQL transformations STEP 2: For existing SQL, Designer will have to have a mechanism to detect new function procedures and re-validate the SQL. We may have to just accept a validation error and force the user to open T-Editor and re-validate? or reselect the function? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1309?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1309: ----------------------------------- Attachment: (was: New View Procedure Wizard.bmml) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira