If you are the only person using a PC, then the concept of having to lock information is totally foreign, because all of the data is yours and yours alone. But databases were built for the multi-user world, where concurrent access to the data is the norm. To handle this, we sometimes need to lock the data to ensure it is controlled and updated in a way that guarantees integrity and correctness. In this episode, we discuss the "Optimistic" and "Pessimistic" locking strategies, how they are used to handle the "Lost Update" problem, and what role the internet played in changing our view of database locking. If you like this episode, be sure you hit the Like button and share it with your colleagues. Catch me on Twitter at https://twitter.com/connor_mc_d  if you have comments or questions. Blog post referred to in the episode: https://stewashton.wordpress.com/2017/06/17/avoiding-lost-updates-with-ora_rowscn/