Closed dpoirier closed 8 years ago
Happily, this glitch was resolved, as is detailed in the Basecamp issue. It turned out that some old tables from the previous year, orphaned when the upgrade added symposion_
to the beginning of each table name and re-created them as new tables, were still sitting around with foreign key references still pointing at the old proposals, that Django could not delete because it had no models telling it that the old tables were there. The old tables were removed, and the purging of the proposals table was able to proceed without further problems.
(For those with access to the basecamp project, https://basecamp.com/1849796/projects/9507827/messages/48756075#comment_335788247)