[ https://issues.jboss.org/browse/TEIID-3658?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3658: --------------------------------------- Sorry I was mixing up vdb service and vdbrepository service. As for adding the transports as dependencies to a vdb service that is something that seems more like a feature than a bug fix - as we could then also restrict the access of the vdb to only a subset of transports. It's just continuity for those who have never enabled odbc access - then this metadata will not show up anywhere. As it could in theory cause an unintended issue for someone that previous did not have odbc access enabled and has a pg source that exposes pg system tables. Now user queries would need qualification where none was needed before. It seems like we can: 1. add a listener to the vdbrepository service based TranportAdd 2. or make the odbc metadata enabled configuration part of the teiid subsystem and default to true, so that we would preserve the option to disable it -- This message was sent by Atlassian JIRA (v6.3.15#6346)