Changes between Version 3 and Version 4 of Conceptual Design – ER Diagram and Data Requirements

Timestamp:

08/26/25 13:18:34 (7 days ago)

Author:

221531

Comment:

--

Conceptual Design – ER Diagram and Data Requirements

@@ -109 +109 @@
     **''is_located_at''** – a relation which indicates that a restaurant is located at one location, and a location can have only 1 restaurant.
 === 1:M ===
-* User → Address  \\
-    **''has''** – a relation which indicates that a user can have multiple addresses, and an address can belong to one user.
+
 
 * Customer → Order  \\
     **''has''** – a relation which indicates that a user can have multiple addresses, and an address can belong to one user.
 === M:N ===
+* User ↔ User Adresses ↔ Address  \\
+    **Junction: ** User Adresses solves M:N of User and Address, by storing the composite key (user_id, address_id)\\
+
+    **''has''** – relation between User and User Addresses where a user can have multiple addresses.\\
+
+    **''belongs''** – relation between Address and User Addresses where an address can belong to multiple users.\\
+\\