Right, that would be the 'with no respect for its previous state' option, which is easier but more limited since it means you have to duplicate items every single time you want to do it.

Screwing up databases is so damn easy, though. The real question to me is how it slipped through QA's fingers - are they just skipping production client validation or is SE slipping last-second changes into the tables?