[ https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2584: ------------------------------------- I was thinking write "SYSADMIN" procedure so that we track them admin procedures, but opting to put them in the same schema as the view is. I thought I could use "DYNAMIC SQL" for managing, but realized I need to use procedure language. So, I am adding them as normal virtual procedures. I also changed "load" procedure such that it returns TABLE, which is nothing but loaded materialized view, then I can simply run this procedure to load (if needed) then select the rows needed. By allowing user to define where the status table as the metadata, I left the decision back on to user. It is expectation that they use single copy of it. If used by user, Teiid documentation will provide the table structure that user need to create. (or tooling will fill this gap). What are naming/versioning I should be concerned about? I am also thinking, if "load" procedure already exists in the schema, the override "load" method should not be generated. native procedures, but expectation is user is wrapping them in the "native" procedure to begin with, such that "load" method is just pre-canned template just replaces the values. One thing I am struck is, how I could execute this non-blocking manner? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira