Changes between Version 3 and Version 4 of Additional Integrity Constraints


Ignore:
Timestamp:
05/13/26 20:08:49 (13 days ago)
Author:
193284
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Additional Integrity Constraints

    v3 v4  
    55This section documents additional CHECK and UNIQUE constraints implemented during the advanced database development phase.
    66
     7The constraints improve data integrity by restricting invalid values and preventing duplicate RSVP and attendance records.
     8
    79=== SQL Code ===
    810
    9 <pre>
     11{{{
     12#!sql
    1013ALTER TABLE event_rsvp
    1114ADD CONSTRAINT chk_rsvp_status
    … …  
    2326ADD CONSTRAINT uq_guest_event_attendance
    2427UNIQUE (guest_id, event_id);
    25 </pre>
     28}}}
     29
     30== Constraint Overview ==
     31
     32* CHECK constraints are used to restrict invalid status values.
     33* UNIQUE constraints prevent duplicate RSVP and attendance records for the same guest and event combination.
     34* Integrity rules are enforced directly at database level independently from the application layer.