[ https://issues.jboss.org/browse/TEIID-5725?page=com.atlassian.jira.plugin... ] Christoph John edited comment on TEIID-5725 at 4/22/19 3:53 PM: ---------------------------------------------------------------- Hello Steven, I came up with a further question regarding virtual procedures. The question is related to transactions. Let's say I have multiple Teiid instances running which access the same mysql database, or alternatively other clients with direct access to the mysql database. Do I explicitly have to wrap my virtual procedures and functions which I write in the ddl file into a transaction? And how would the command syntax for this look like? Further question regarding visibility of stored procedures and functions. I learned from a discussion with Ramesh, that there is a visibility attribute which I can set on the entire schema to set all tables and functions inaccessible. However, in that case I would have to wrap each table, I like to export to odata, into an additional view. This seems like odd extra work for me. My thinking is the following. If I have a stored procedure or function in the source database, I would like to use it within my virtual procedures but at the same time would not like to allow access via odata. Would it be possible to add a visibility option to the procedure definition in the dll definition? Or does something similar already exist? was (Author: cjohn001): Hello Steven, I came up with a further question regarding virtual procedures. The question is related to transactions. Let's say I have multiple Teiid instances running which access the same mysql database, or alternatively other clients with direct access to the mysql database. Do I explicitly have to wrap my virtual procedures and functions which I write in the ddl file into a transaction? And how would the command syntax for this look like? Further question regarding visibility of stored procedures and functions. I learned from a discussion with Ramesh, that there is a visibility attribute which I can set on the entire schema to set all tables and functions inaccessible. However, in that case I would have to wrap each table I like to export to odata into a view, which seems like odd extra work for me. My thinking is the following. If I have a stored procedure or function in the source database, I would like to use it within my virtual procedures but at the same time would not like to allow access via odata. Would it be possible to add a visibility option to the procedure definition in the dll definition? Or does something similar already exist? -- This message was sent by Atlassian Jira (v7.12.1#712002)