Using foreign keys and cascades
I'm looking through the database and seeing that its very easy to end up with orphaned data. Say you have a grid with 40 waypoints and delete the grid table entry while forgetting to remove the 40 waypoints. You now have 40 rows of data in limbo.
Same goes with quest globals. Say charID #5623 goes out and racks up 2000 quest global entries and then the player deletes the character. Now there are 2000 rows of data orphaned and sitting in the database forever.
There is a method to associate tables and data with other tables and data so that if one is changed or deleted, the other follows suit - changing with the original table or being deleted along with the original.
I'm wondering, has this been discussed and rejected or has nobody thought to use it yet?
|
Threaded Mode
