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
When a column is a primary key and foreign key at the same time, only the PK constraint will be shown, even though mermaid supports PK,FK inside the constraint column:
erDiagram
CAR ||--o{ NAMED-DRIVER : allows
CAR {
string registrationNumber PK
string make
string model
}
PERSON ||--o{ NAMED-DRIVER : is
PERSON {
string driversLicense PK "The license #"
string name
}
NAMED-DRIVER {
string carRegistrationNumber PK, FK
string driverLicence PK, FK
}
Loading
I will create a PR, as this is a necessary feature to start with the PR for #43.
The text was updated successfully, but these errors were encountered:
* Support multiple key constraints on a single attribute (#51)
* Add unique constraint to key column (#43)
* Relationship labels (#50)
* Adds relationship label types and parser
* Lookup label based on pk and fk names; overrides omitting the label and the constraint label
* First full working version
* Use a map for faster lookup
* Fix example labels
* Adds comments for label regex
* Adds basic tests for relationship label map
* Support multiple key constraints on a single attribute (#51) (#52)
* Add unique constraint to key column (#43)
---------
Co-authored-by: Dan Goslen <dwgoslen@gmail.com>
When a column is a primary key and foreign key at the same time, only the
PK
constraint will be shown, even though mermaid supportsPK,FK
inside the constraint column:I will create a PR, as this is a necessary feature to start with the PR for #43.
The text was updated successfully, but these errors were encountered: