[
https://issues.jboss.org/browse/TEIIDDES-1846?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1846:
----------------------------------------
If I default the SQL for a new Virtual Table in the New... wizard to *SELECT '<sql
undefined>'*, then the resulting SQL will be valid BUT the table will end up with a
generated column named: *expr1*. The Transformation Notification framework does a
Resolve on the SQL and auto-generates the column/symbol. Not sure that's the behavior
we want.
Top Down modeling, when importing to create views, allow for default
syntax to applied
--------------------------------------------------------------------------------------
Key: TEIIDDES-1846
URL:
https://issues.jboss.org/browse/TEIIDDES-1846
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Reporter: Van Halbert
Assignee: Barry LaFond
Fix For: 8.5
When a user is starting from a top-down approach (building the views) to design their
data layers, and will be performing an import to create the view layer, it would speed up
the iterative development of build / deploy / test (not preview) if when the view is built
(on import), it can contain valid syntax so that the model will validate. Example of
syntax could be, "Select '1'" or "Select 'view not
defined'" or throw an exception. This would enable the modeler to implement the
views at their pace and have it deployable, rather than having to go thru every view and
add syntax before its valid. This is akin to JAVA and NOOP'ing the methods.
--
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