I typically get annoyed when people try to define a concept purely "by example"... ... but YOUR video and YOUR example (done in MS Access) actually resulted in MSAccess displaying some pop-up windows which REALLY DROVE HOME some key points about what Referential Integrity IS: The invoking of a set of rules-based EVENT MONITORING and EVENT HANDLING on a set of tables, the DATA they CONTAIN and the RELATIONSHIPS they POSSESS, between which a RELATIONSHIP has been DEFINED. SO if "Referential Integrity" is a RULES-BASED EVENT-HANDLING MECHANISM which you "invoke", this begs the questions: - WHICH "events" ? and - WHICH "rules" ? ANSWERS: EVENTS Being Monitored when Referential Integrity is "invoked" (enforced) between any 2 tables: - ADDING a row to the REFERENCING table; - ADDING/CHANGING a VALUE in REFERENCING FIELD (aka 'foreign key') - DELETING/CHANGING a row in the REFERENCED table; and maybe a few others RULES being enforced when Referential Integrity is being "invoked" (enforced) between any 2 tables: - REFERENCING value MUST EXIST as a PrimaryKey in the REFERENCED table; - REFERENCED PrimaryKey cannot be Null - REFERENCING value cannot be Null Your video and its pop-up error illustrated this better than most videos. :-)
Best Explanation !! "the Detailing" in explanation in mind blowing!
What a nice voice, and a great tutorial! Thank you,,,
Good explanation.
Brilliant. Very well explained in a concise manner
I didn't learn anything. Your voice is hypnotizing.
Great Video
Superb!!!
love the voice of the tutor in this vid!
hello, when do I tick the enforce referential integrity box ?
Intereseting but not what I was looking for, thought you ll talk about Referencial Actions which is part of ref integrity.
I typically get annoyed when people try to define a concept purely "by example"...
... but YOUR video and YOUR example (done in MS Access) actually resulted in MSAccess displaying some pop-up windows which REALLY DROVE HOME some key points about what Referential Integrity IS: The invoking of a set of rules-based EVENT MONITORING and EVENT HANDLING on a set of tables, the DATA they CONTAIN and the RELATIONSHIPS they POSSESS, between which a RELATIONSHIP has been DEFINED.
SO if "Referential Integrity" is a RULES-BASED EVENT-HANDLING MECHANISM which you "invoke", this begs the questions:
- WHICH "events" ? and
- WHICH "rules" ?
ANSWERS:
EVENTS Being Monitored when Referential Integrity is "invoked" (enforced) between any 2 tables:
- ADDING a row to the REFERENCING table;
- ADDING/CHANGING a VALUE in REFERENCING FIELD (aka 'foreign key')
- DELETING/CHANGING a row in the REFERENCED table;
and maybe a few others
RULES being enforced when Referential Integrity is being "invoked" (enforced) between any 2 tables:
- REFERENCING value MUST EXIST as a PrimaryKey in the REFERENCED table;
- REFERENCED PrimaryKey cannot be Null
- REFERENCING value cannot be Null
Your video and its pop-up error illustrated this better than most videos. :-)
Excellent job of showing and explaining what referential integrity is!
very well explained!
Are the people liking this video just for the voice, or is the content good as well?
thanks a lot
Thank you for this
I know her and she is kind of old so don't fantasize about her. :P
sexy voice
Moron.