Handle adding empty optimization data #169
Open
+81
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In message_ix, we may iterate over all variables etc of one
Scenario
(backed by aRun
) to add them to anotherScenario
(backed by anotherRun
), which may include adding empty data ({}
orpd.DataFrame()
) to them. This should be working already as only the combination of existing and new data are validated.However, this led to an error for indexsets because adding an empty list violates one of the
UniqueConstraint
s for their underlying tables. So I was adjusting that already and figured the remaining items would also benefit from tests covering this case.On top of which, I figure we don't need to bother the DB or validate data when adding empty data. This PR avoids that, which should make the code more performant.
NOTE: I'm also using this branch right now for some temporary debug commits.