[GH-ISSUE #92] Error running riab --cleanup #57

New issue

Closed

opened 2026-03-23 20:28:45 +00:00 by mirror · 1 comment

mirror commented

2026-03-23 20:28:45 +00:00

Owner

Originally created by @JensCardon on GitHub (Jul 29, 2024).
Original GitHub issue: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/issues/92

Running the riab --cleanup command results in foreignkey vialation errors for Azure SQL Server Databases.

Possible fix: replace TRUNCATE by DELETE statements

Note: if not already implemented, work tables should be cleaned as well when running the cleanup command.

Originally created by @JensCardon on GitHub (Jul 29, 2024). Original GitHub issue: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/issues/92 Running the riab --cleanup command results in foreignkey vialation errors for Azure SQL Server Databases. Possible fix: replace TRUNCATE by DELETE statements Note: if not already implemented, work tables should be cleaned as well when running the cleanup command.

mirror

2026-03-23 20:28:45 +00:00

closed this issue
added the
invalid
label

mirror commented

2026-03-23 20:28:46 +00:00

Author

Owner

@pjlammertyn commented on GitHub (Sep 3, 2024):

This is incorrect!
Before the cleanup, riab disables all the constraints: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/blob/main/src/riab/etl/sql_server/cleanup.py#L32

Riab is not aware if you add additional constraints.

@pjlammertyn commented on GitHub (Sep 3, 2024): This is incorrect! Before the cleanup, riab disables all the constraints: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/blob/main/src/riab/etl/sql_server/cleanup.py#L32 Riab is not aware if you add additional constraints.