Failing `0006_batch_edit` migration prevents data sets from opening

[lexiclevenger]

Describe the bug
An error is thrown when trying to open or create a WB data set on some databases. Only occurs in production and does not occur if the database is opened in a previous version.

These are the only affected databases I know of:
KUPaleoBot_2024_06_06
KU_Fish_Tissue_2024_01_24

To Reproduce
Steps to reproduce the behavior:

1. Go to the WorkBench
2. Click on a data set or 'Create New'
3. See error

Expected behavior
The WorkBench should open with no error.

Screenshots
Creating a data set:

Screen.Recording.2025-05-13.at.11.43.17.AM.mov

Specify 7 Crash Report - 2025-05-13T16_45_59.623Z.txt

Opening a data set:

Screen.Recording.2025-05-13.at.11.44.26.AM.mov

Specify 7 Crash Report - 2025-05-13T16_45_35.263Z.txt

Please fill out the following information manually:

• OS: Mac
• Browser: Chrome
• Specify 7 Version: 7539ceb
• Database Name: KU_Fish_Tissue_2024_01_24
• Collection name: KU Fish Voucher
• User Name: spfishadmin
• URL: https://kufishtissue20240124-production.test.specifysystems.org/specify/

[sharadsw]

On KU fish this seems to be happening due to a migration error. Some workbench migrations never ran. Looks like the 0006_batch_edit migration failed. Not sure why that would happen since it's an autogenerated migration.

workbench
 [X] 0001_initial
 [X] 0002_spdataset_visualorder
 [X] 0003_auto_20210218_1256
 [X] 0004_auto_20210219_1131
 [X] 0005_auto_20210428_1634
 [ ] 0006_batch_edit
 [ ] 0007_spdatasetattachment
 [ ] 0008_spdataset_rolledback

One possible explanation is that this db was already used with the old batch edit PR (#4929) which had 3 different migrations for batch edit. The db probably already has the required fields from that PR and cannot run the new batch edit migration. The error I get when trying to manually migrate also indicates that

django.db.utils.OperationalError: (1060, "Duplicate column name 'isupdate'")

[sharadsw]

Same problem with the KUPaleoBot db

workbench
 [X] 0001_initial
 [X] 0002_spdataset_visualorder
 [X] 0003_auto_20210218_1256
 [X] 0004_auto_20210219_1131
 [X] 0005_auto_20210428_1634
 [ ] 0006_batch_edit
 [ ] 0007_spdatasetattachment
 [ ] 0008_spdataset_rolledback

[sharadsw]

Should now be fixed for both these dbs. I faked the 0006 migration and applied the migrations after that one. Faking the 0006 migration shouldn't cause any problems here since the db already has the fields that migration was going to add.

[grantfitzsimmons]

Closing this for now but this issue can be a reference if we see the behavior in the future