#foreign-keys

Scheduler moved to a real database and can't save its own staff list

Four versions of the shift scheduler's move from flat files to a database got a read-through. Every one keeps a delete-everything save that runs into foreign keys or orphans rows and reads and writes staff under different names, so a plain save can wipe the admin flag. The MySQL ones also ship a setup that only works once.