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
I've seen in some diagrams (maybe historical) there was a config/directive that allowed "rank" to be passed which helped control the position of nodes/entities in a diagram.
Use case: When an ERD has 5+ entities connected to a single entity via relationships, this can be visually displeasing and get messy. To allow for "moving" of entities to certain levels, the "rank" here would help
This will show 5 entities below CUSTOMER if dropped in the Live Editor. Would like to make it more true to a "Star" schema where Customer is at its own "level", Mailing-Address and Shipping Address are at its own level, Payment Methods and User-Profile at its own level
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Proposal
I've seen in some diagrams (maybe historical) there was a config/directive that allowed "rank" to be passed which helped control the position of nodes/entities in a diagram.
Use case: When an ERD has 5+ entities connected to a single entity via relationships, this can be visually displeasing and get messy. To allow for "moving" of entities to certain levels, the "rank" here would help
Example
title: Order example
erDiagram
CUSTOMER ||--o{ ORDER : places
ORDER ||--|{ LINE-ITEM : contains
CUSTOMER }|..|{ MAILING-ADDRESS : uses
CUSTOMER }|..|{ SHIPPING-ADDRESS : uses
CUSTOMER }|..|{ PAYMENT-METHODS : uses
CUSTOMER }|..|{ USER-PROFILE : has
This will show 5 entities below CUSTOMER if dropped in the Live Editor. Would like to make it more true to a "Star" schema where Customer is at its own "level", Mailing-Address and Shipping Address are at its own level, Payment Methods and User-Profile at its own level
Screenshots
No response
The text was updated successfully, but these errors were encountered: