[
https://issues.jboss.org/browse/TEIIDDES-2466?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-2466:
------------------------------------------
This is a good enhancement. A couple of notes from our meeting:
- use a uuid to prevent vdb collisions
- be aware that procedures can get quite complex and may pull in a lot of metadata,
especially when nested. It may be good to put a check in based upon the ddl size, such as
10 megs, that will prevent the preview deployment
- usage of dynamic sql or references to the system metadata tables in theory need the
entire vdb to make sense, so you may have to disallow preview for them
Create Preview VDB for only the model containing the table that is
being preview
--------------------------------------------------------------------------------
Key: TEIIDDES-2466
URL:
https://issues.jboss.org/browse/TEIIDDES-2466
Project: Teiid Designer
Issue Type: Feature Request
Components: Data Preview, Documentation, Patch Release
Affects Versions: 9.0
Reporter: Debbie Steigner
Assignee: Barry LaFond
Fix For: 10.0.1
Attachments: custom-preview-data-preview-sql-tab.png,
custom-preview-data-preview-vdbxml-tab.png,
data-source-definition-options-jdbc-import.png,
data-source-definition-options-page-flat-file.png
RFE
Currently once you preview one table a Preview VDB is created for all the models in the
project, request that the Preview VDB only be created for the model containing the table
that is being previewed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)