I disagree. There is no significant advantage with the current design (it would be nice with a thread pool), it will only run 1 query at a time, and if the account query fails it is not a good idea to run any other queries. However, asyncLoadAccount should **never** fail because account_id has a foreign key with ON DELETE CASCADE, so if the account doesn't exist, the player shouldn't exist either.