[
https://issues.jboss.org/browse/TEIIDDES-2100?page=com.atlassian.jira.plu...
]
Barry LaFond edited comment on TEIIDDES-2100 at 5/9/14 4:16 PM:
----------------------------------------------------------------
Solution would have to:
* Take one or more models (Source and view models with dependencies)
* Search for ANY table names with "." char in them
* Add Double-Quotes to the object names
* Fix ANY Transformation SQL containing the original non-quoted names by adding
appropriate quoting
Basic naming rules which include '.' delimeter (Teiid runtime)
* column and schema names can NOT included the '.' delimiter
* Table names can include '.' delimiters, but more than one '.' is
discouraged and not expected.
was (Author: blafond):
Solution would have to:
* Take one or more models (Source and view models with dependencies)
* Search for ANY table names with "." char in them
* Add Double-Quotes to the object names
* Fix ANY Transformation SQL containing the original non-quoted names by adding
appropriate quoting
Add ability to migrate older models containing table names with
"." characters
------------------------------------------------------------------------------
Key: TEIIDDES-2100
URL:
https://issues.jboss.org/browse/TEIIDDES-2100
Project: Teiid Designer
Issue Type: Feature Request
Components: Transformations, Validation
Affects Versions: 8.4, 8.3.2
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 8.5, 8.3.3
DV 6 tooling (Designer 8.3.x) includes error validation to prevent non-quoted names from
being defined and used in SQL.
Designer needs a mechanism/framework to help users globally fix table names containing
the "." delimiter.
Options:
# Designer feature/action to "fix" a model
# simple CLI-based app to apply to a model
Need to investigate our "rename" logic to see if it can handle the cascade
effect of changing table name and fixing dependent SQL
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)