It has been a really interesting time figuring out how we're going to store and update our SQL database for the potential feature of notifying registered users (another potential feature) that a class that they chose for their schedule has changed. We've had to change routes a couple times already, and know that what we were doing wouldn't quite work correctly. We still have quite a bit to discuss to figure out exactly how we are going to implement our database structure for this feature. One thing that we do know is that it will most likely have some sort of global version control that we will then utilize for various things such as deleting old versions, and comparing old version data to the new version data to look for differences.