Changes between Version 6 and Version 7 of P5
- Timestamp:
- 01/28/26 08:51:59 (13 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
P5
v6 v7 26 26 27 27 This relation violates normalization principles. 28 29 Note: venue_type in the UNF is an attribute that is later normalized into a separate relation. 28 30 29 31 === Denormalized Table === … … 64 66 65 67 This confirms that the initial relation has a composite primary key, which leads to partial dependencies. 68 This composite key is minimal because removing any attribute (user_id, wedding_id, venue_id, or booking_date) results in ambiguity and loss of uniqueness. No proper subset of this key functionally determines all attributes of R. 66 69 67 70 == First Normal Form (1NF) == … … 161 164 || venue_booking || booking_id || One booking per ID || 162 165 163 This ensures entity integrity .166 This ensures entity integrity and in all resulting relations, no non-key attribute functionally determines another non-key attribute. 164 167 165 168 Please review the proof explained in more details here -> [[Proof of 3N]]
