Dynamic VDB named attributes in mapping statement are not automatically mapped to the corresponding column in the table definition
Issue
- Dynamic VDB View model - named attributes in mapping statement are not automatically mapped to the corresponding column in the table definition
- Unexpected sequential dependency between virtual table column order and mapping column sequence.
The statement to create a virtual table:
CREATE VIEW TargetModelViewName (
ColumnA …
ColumnB …
ColumnC …) …
AS SELECT
SourceModel.SourceTable.ColX AS ColumnA,
SourceModel.SourceTable.ColY AS ColumnC,
SourceModel.SourceTable.ColZ AS ColumnB;
- DV doesn't map ColY to ColumnC, it maps ColZ because of the order.
Environment
- Red Hat JBoss Data Virtualization (DV) 6.2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.