Fix Version/s: None
(original description is no longer accurate; see comments)
Registry's provenance tables - execution, run, and quantum - can't currently be fully populated without having database updates. For example: you can't insert a dataset until after its run has been inserted; you can't insert a run until you've inserted the execution it inherits its ID from; you can't insert an execution until after it's completed, because it has an end timestamp field. Work through low-level use cases for these tables and ensure we can actually have all of their values when it's time to insert them, splitting up tables as necessary.
, Christopher Stephens [X] : this ticket exists because I'm assuming updates are a problem. Please let me know if they aren't or if you have any expections/requirements/wisdom on when various provenance records should be inserted relative to the datasets they refer to.
- is contained by
DM-21231 Refactor Registry handling of dataset and associated tables