[GH-ISSUE #67] Running the --cleanup on one table, should also cleanup the dependent tables in the ETL flow. #38

Closed
opened 2026-03-23 20:28:40 +00:00 by mirror · 1 comment
Owner

Originally created by @pjlammertyn on GitHub (May 23, 2024).
Original GitHub issue: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/issues/67

Originally assigned to: @pjlammertyn on GitHub.

Because the --cleanup command triggers the generation of new auto numbered id's (in the next ETL run), the foreign keys of the dependent tables will have invalid wring foreign keys to that table.

So all the dependent tables should also be cleared!

Originally created by @pjlammertyn on GitHub (May 23, 2024). Original GitHub issue: https://github.com/RADar-AZDelta/Rabbit-in-a-Blender/issues/67 Originally assigned to: @pjlammertyn on GitHub. Because the *--cleanup* command triggers the generation of new auto numbered id's (in the next ETL run), the foreign keys of the dependent tables will have invalid wring foreign keys to that table. So all the dependent tables should also be cleared!
mirror 2026-03-23 20:28:40 +00:00
Author
Owner

@pjlammertyn commented on GitHub (May 30, 2024):

For example if you cleanup the person table.

riab --cleanup person

All dependent tables in the ETL flow, must also be cleaned up!

└──person
  ├──condition_era
  ├──death
  ├──dose_era
  ├──drug_era
  ├──episode
  ├──observation_period
  ├──payer_plan_period
  ├──specimen
  └──visit_occurrence
    ├──episode_event
    └──visit_detail
      ├──condition_occurrence
      ├──device_exposure
      ├──drug_exposure
      ├──measurement
      ├──note
      ├──observation
      └──procedure_occurrence
        └──note_nlp
<!-- gh-comment-id:2139581192 --> @pjlammertyn commented on GitHub (May 30, 2024): For example if you cleanup the **person** table. ```bash riab --cleanup person ``` All dependent tables in the ETL flow, must also be cleaned up! ``` └──person ├──condition_era ├──death ├──dose_era ├──drug_era ├──episode ├──observation_period ├──payer_plan_period ├──specimen └──visit_occurrence ├──episode_event └──visit_detail ├──condition_occurrence ├──device_exposure ├──drug_exposure ├──measurement ├──note ├──observation └──procedure_occurrence └──note_nlp ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
RADar-AZDelta/archived-Rabbit-in-a-Blender#38
No description provided.