Details
-
Enhancement
-
Resolution: Done
-
Major
-
3.3.0.Final
-
None
Description
Currently Teiid DDL generation from deployed VDBs cannot guarantee the order of the tables defined in the DDL. (actually alphabetical now) If a FK constraint is in-line and references a table yet parsed in the DDL file, no TableReference AST node will be found and no reference value will be set.
This leads to incorrect models via Teiid Connect importer in Teiid Designer.
Fix would be to capture the constraint nodes (FK ast nodes) that need to get resolved and have the DDL parser framework implement a postProcess() method, or something like it.