返回
-
标题
Cannot create two view relationships to same table -
说明
TDM does not allow self-referential view relationships; i.e., joining a table to itself.
I created the view ContentSibling with two relationships to a ContentSoftware table, one aliased as ‘ce’ and the other as ‘sib’. However, after adding the ce.ContentId and ce.EkitId columns, it won’t allow me to add the sib.ContentId column. Apparently because there is already a ContentId column in the list.But aliasing the column doesn’t help; it exhibits the same behavior. Worse, if I delete the ce.ContentId column and then add the sib.Contentid column, it adds the ce.ContentId column, instead.I believe that, even though the table is aliased, it continues to rely upon the entity name rather than the alias name so it won’t allow adding the other reference.