Changes between Version 3 and Version 4 of ERModel

Timestamp:

01/09/26 09:57:32 (12 days ago)

Author:

193284

Comment:

Simplified the model by removing Church_booking and modeling a direct 1:1 relationship between Wedding and Church.

ERModel

@@ -236 +236 @@
 
 
-== **Entity: Church_booking**
-
-Explanation:
-The Church_booking entity records church reservations for wedding ceremonies.
-
-**Candidate keys:**
-booking_id – chosen as the primary key.
-
-**Attributes:**
-booking_id – numeric, required
-date – date, required
-start_time – time, required
-end_time – time, required
-status – text, required
-
-
 == **Entity: Priest**
 
@@ -304 +288 @@
 * Constraint: no overlapping bookings for the same Photographer.
 
-=== Wedding – Church_booking – Church
-* One Wedding can have many Church_bookings (1:N).
-* One Church can be booked many times (1:N).
-* Constraint: no overlapping bookings for the same Church.
+=== Wedding – Church
+
+Each Wedding is associated with exactly one Church (1:1).
+Each Church is associated with at most one Wedding for a given date and time.
+This relationship reflects the real-world assumption that a wedding ceremony is held in a single church.
+Since the relationship is 1:1 and no additional booking-specific attributes are required, a separate Church_booking entity is not needed.
+Constraint: a Church cannot be assigned to more than one Wedding at the same date and time.