Changes between Version 3 and Version 4 of Proof of 1N form

Timestamp:

01/27/26 23:44:58 (13 days ago)

Author:

213087

Comment:

--

Proof of 1N form

@@ -7 +7 @@
 === Example of UNF Data ===
 
-|| user_id || user_first_name || user_last_name || user_email || wedding_id || wedding_date || wedding_budget || venue_id || venue_name || venue_type || venue_capacity || booking_id || booking_date || start_time || end_time ||
-|| U01 || Ana || Petrova || ana@mail.com
- || W01 || 2026-06-12 || 15000 || V01 || Grand Hall || Ballroom || 300 || B01 || 2026-06-12 || 18:00 || 23:00 |
-|| U01 || Ana || Petrova || ana@mail.com
- || W01 || 2026-06-12 || 15000 || V02 || Garden Venue || Outdoor || 200 || B02 || 2026-06-12 || 12:00 || 16:00 |
-|| U02 || Marko || Iliev || marko@mail.com
- || W02 || 2026-09-20 || 20000 || V01 || Grand Hall || Ballroom || 300 || B03 || 2026-09-20 || 19:00 || 01:00 |
+|| user_id || user_first_name || user_last_name || user_email || wedding_id || wedding_date || wedding_budget || venue_id || venue_name || venue_type || venue_capacity || booking_id || booking_date || start_time || end_time 
+|| U01 || Ana || Petrova || ana@mail.com|| W01 || 2026-06-12 || 15000 || V01 || Grand Hall || Ballroom || 300 || B01 || 2026-06-12 || 18:00 || 23:00 
+|| U01 || Ana || Petrova || ana@mail.com|| W01 || 2026-06-12 || 15000 || V01 || Garden Venue || Outdoor || 200 || B02 || 2026-06-12 || 12:00 || 16:00 
+|| U02 || Marko || Iliev || marko@mail.com|| W01 || 2026-09-20 || 20000 || V01 || Grand Hall || Ballroom || 300 || B03 || 2026-09-20 || 19:00 || 01:00 ||
 
 === Why This Relation Is UNF ===
 
--Repeating groups exist:
+**-Repeating groups exist:**
 
 
 --User and wedding data are repeated for each venue booking
 
--Redundancy:
+**-Redundancy:**
 
 
@@ -28 +25 @@
 --User information appears multiple times
 
--Update anomalies:
-
+**-Update anomalies:
+**
 
 --Changing a venue name requires updating multiple rows
 --Changing a user email risks inconsistent data
 
--Insertion anomalies:
+**-Insertion anomalies:**
 
 
@@ -40 +37 @@
 --A user cannot exist without a wedding
 
--Deletion anomalies:
+**-Deletion anomalies:**
 
 
@@ -48 +45 @@
 Storing all data together leads to redundancy and update anomalies.
 
-Identified Functional Dependencies (FDs):
+
+
+**Identified Functional Dependencies (FDs):**
 
 -user_id → user_first_name, user_last_name, user_email
+
+
 -wedding_id → wedding_date, wedding_budget, user_id
+
+
 -venue_id → venue_name, venue_type, venue_capacity
+
+
 -booking_id → venue_id, wedding_id, booking_date, start_time, end_time