[ https://jira.jboss.org/jira/browse/TEIID-231?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-231: --------------------------------- Component/s: Connector API Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] Having a function definition file with the connector does fix the runtime problem, but we would still need to update the designer to understand having some association between a physical model and a function definition model. It makes more sense to me to merge function definitions with the standard relational model. All of our natural scoping rules (in terms of naming and association with a physical source) would apply. Built-in functions would be added to the system model. With this design a function definition model would just be a virtual model with nothing but functions and could be added to any vdb that needs to support a common set of udfs. If and whenever we have vdb reuse you could then have a global function definition vdb. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira