Skip to content

Conversation

@labkey-jeckels
Copy link

Rationale

DatabaseDiagnosticsTest is failing due to orphaned laboratory.workbooks rows that are missing their core.container row. A hard FK might be useful here, but it's possible that it would need to do a cascading delete of existing orphaned rows so keeping it simple for now.

Changes

  • Delete for workbook containers as well as parent containers

@labkey-jeckels labkey-jeckels merged commit 8473d76 into develop Sep 16, 2020
@labkey-jeckels labkey-jeckels deleted the fb_containerDelete branch September 16, 2020 14:45
@bbimber
Copy link
Collaborator

bbimber commented Sep 16, 2020

@labkey-jeckels I believe the behavior of leaving the rows in laboratory.workbooks used to be by design, since that table used to be the table of record for workbook ID, and if we deleted a workbook we wanted to skip over that number. however, a long time ago LabKey started numbering workbooks incrementally by container, and we now defer to LK's numbering. I think your change is fine.

I just have one question: did DatabaseDiagnosticsTest change or become more robust recently? I think the laboratory.workbooks purge (or lack of purge) behavior was fairly old.

@labkey-jeckels
Copy link
Author

OK, thanks for confirming.

The test hasn't changed, but it just started running in a suite that happened to exercise the lab workbook tests

bbimber added a commit that referenced this pull request Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants