Database design - ERD. Modeling Question
Hopefully someone may be able to quickly advise the best way for me to model my ERD (I'm using IDEF1X & ERWin not Chen Notation) although it doesn't really matter.
Basically I have Three Entities
- Organisation
- Person
- Trustee
Business rules state that a Trustee can be either a person or organisation.
My question is, would it be correct to have two primary, foreign key relationships to Trustee. One from Organisation > Trustee and the second from Person > Trustee. Where one of the FK fields of Trustee will always be NULL depending on if the Trustee is a person or organisation.
Or would it be better to have some sort of associative table between person and organisation (person_organisation) and create a PK, FK relationship from person_Organisation > Trustee.
The second option seems better as there might be other entities that also need to link to both Organisation and person.
Hopefully that makes sense.
Many many thanks in advance
EDIT
Well, this should work too:
- "Dynamic" tables in SQL?
- How to programmatically check if row is deletable?
- How does PostgreSQL enforce the UNIQUE constraint / what type of index does it use?
- How do I structure data common to all users in Cloud Firestore?
- Table constraint for range and null values
- Calculating and saving space in PostgreSQL
- How would you set up a database to handle comments for a blogging site?
- How do multi user applications use databases?
- Why is read repair not sufficient in making dynamo-style database linearizable?
- Get table and column "owning" a sequence
- Can you define a foreign key in a table from which the table with the primary key is derived?
- How entity framework works for large number of records?
- Do pizza toppings exist on their own in 3NF or does the column 'toppings' fail 2NF because it does rely on the pizza in practical reality?
- How to generate a diagram of a very large database schema (SQL Server)
- Custom cascade delete stored procedure for temporal tables in SQL Server
- Database Management: Where to store old data outside the database
- Saving barcode number in database that is generated with the logic
- Generalizing work orders database table design
- Removing a table without a unique index / constraint
- Dropping column in Postgres on a large dataset
- Cannot add or change a record because a related record is required in table 'COMPANY'
- Consolidating tables with one-to-one relationships
- How do I relate requesters of different type?
- How to model Student/Teacher/Class with DynamoDb?
- follower/following relationship
- What is the recommended collation for a PostgreSQL unique e-mail column?
- ERD diagram Confusion
- What are proper table-naming conventions for many-to-many intersect tables?
- (Database Design - products attributes): What is better option for product attribute database design?
- Representing a plant with definite genus but unknown species