[db] Sometimes updater will set incorrect foreign keys

After update, it seems that sometimes the foreign keys are not correct, for example:

users table will be renamed as users__back during update, and for some reason, after restoring the data, the referenced table(s) might contain something like:

CONSTRAINT addresses_fk1FOREIGN KEY (user_id) REFERENCESusers__back`(id)

which will throw an exception because users__back no longer exists.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information