According to wikipedia, consistency is more about keeping the DB always in a state that respects the rules: Consistency ensures that a transaction can only bring the database from one consistent state to another, preserving database invariants: any data written to the database must be valid according to all defined rules, including constraints, cascades, triggers, and any combination thereof. This prevents database corruption by an illegal transaction. Referential integrity guarantees the primary key-foreign key relationship
i think this concern is addressed in the video during the discussion that a consistent database is a database that respects the invariants -- for example the invariant that there is always at least one worker listed for a given shift. (it's interesting that some of the invariants are user defined and some are internal to the database, for example foreign key references -- so maybe part of the expectation would be that a database will always pass an integrity check pragma or something)
All these beginning videos are almost completely ripped off of "Designing data intensive applications" by Martin Kleppmann. In the future I'll start to diverge from this book and then will attach them.
@@chrisrectenwald7307 Lol yeah I hate reading too, alas sometimes you must, that being said I think this still has supplemental value as visual examples
the smiley logo on the tshirt for ACID topic. hats off on the effort Jordan
According to wikipedia, consistency is more about keeping the DB always in a state that respects the rules:
Consistency ensures that a transaction can only bring the database from one consistent state to another, preserving database invariants: any data written to the database must be valid according to all defined rules, including constraints, cascades, triggers, and any combination thereof. This prevents database corruption by an illegal transaction. Referential integrity guarantees the primary key-foreign key relationship
Yeah that's fair to say, just mainly the database doesn't go bonkers due to multithreading.
i think this concern is addressed in the video during the discussion that a consistent database is a database that respects the invariants -- for example the invariant that there is always at least one worker listed for a given shift. (it's interesting that some of the invariants are user defined and some are internal to the database, for example foreign key references -- so maybe part of the expectation would be that a database will always pass an integrity check pragma or something)
wow, congratzz, you survived the first wave
Yeah I'll probably post something about that later today
okay. I was under my table after the foot picture transaction
That'll be $5
no foot pics no $$$. work hard play hard@@jordanhasnolife5163
@@jordanhasnolife5163 double it and give it to the next person🙏
Feels like a fever dream watching this now getting hit with the bath water
sir not the riley reid
Whoa how'd you get a hold of my browser history?? 🤔
Hey yo.
You should provide the readings that helped you come up with this vidya
All these beginning videos are almost completely ripped off of "Designing data intensive applications" by Martin Kleppmann. In the future I'll start to diverge from this book and then will attach them.
@@jordanhasnolife5163 So you're saying that I should just read the book that I bought.
@@chrisrectenwald7307 lol maybe? there are 1,000 beginner python tuts in video, books, blogs... choose the medium, style that you like
@@chrisrectenwald7307 Lol yeah I hate reading too, alas sometimes you must, that being said I think this still has supplemental value as visual examples