You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The definition should be flexible by assigning a "Relation Type" (any text) to a relation
The output for different relations should not be mixed but separated:
separate diagrams
separate columns in list views
Current Behavior
only one relation type exists: FK-PK-relation
virtual FK-PK-relations relations can be defined using SchemaMeta XML
Possible Solution
when the new planned XMLSchema will be implemented, based on database.schema.table.column (additional to the existing schema based on table.column) this could be implemented.
The text was updated successfully, but these errors were encountered:
Expected Behavior
it should be possible to document several relation types:
The definition should be flexible by assigning a "Relation Type" (any text) to a relation
The output for different relations should not be mixed but separated:
Current Behavior
only one relation type exists: FK-PK-relation
virtual FK-PK-relations relations can be defined using SchemaMeta XML
Possible Solution
when the new planned XMLSchema will be implemented, based on database.schema.table.column (additional to the existing schema based on table.column) this could be implemented.
The text was updated successfully, but these errors were encountered: