I have several applications that share tables. One such is called "attachments."
As part of my upgrade to 2.2.1, I enabled record versioning in each of these apps. I have a specific sequence for opening appadmin in these applications to migrate the tables in case of changes. When I migrated the first application, it created the archive table for attachments. So far, so good. When I attempted to migrate the second application, it also attempted to create the archive table for attachments. Because the table already exists, Psycopg2 raised an exception, 'relation "attachments_archive" already exists.' Is there a way to avoid this? Would it make sense to have tools.enable_record_versioning or dal._enable_record_versioning check for the existence of the archive table before trying to create it? --
