> But assuming that slugs should be unique, we should be checking to make sure we aren't overwriting an existing slug here (but before we update the games table above).

This is actually pretty hard imo. The check for existing slug and the update have to be an atomic operation (or there will be race condition anyway). Still not quite sure how to implement the check and update using one `mult` call, since whether we should enqueue the edit call is dependent on the result of a previous call, but I haven't investigated this thoroughly though.

Having said that, I guess that updating of a slug is *probably* not going to be a very frequent operation, and we might get away with not making the check atomic. :shrugs:

I would rather not perform the check now until it becomes important to verify existing game slugs (probably on another issues with its implication), than to have code that on first sight seem correct but might silently cause problem.