Skip to content

CDA-98 Workaround to updating forecast location for a spec#1647

Open
rma-bryson wants to merge 5 commits intodevelopfrom
bugfix/bad_forecast_spec_behavior
Open

CDA-98 Workaround to updating forecast location for a spec#1647
rma-bryson wants to merge 5 commits intodevelopfrom
bugfix/bad_forecast_spec_behavior

Conversation

@rma-bryson
Copy link
Copy Markdown
Collaborator

…ation id, does not overwrite the original spec, but creates a new one for the new location.

@rma-bryson rma-bryson changed the title Show's that storing a spec with same id-desginator, but different loc… Workaround to updating forecast location for a spec Mar 23, 2026
@rma-bryson rma-bryson force-pushed the bugfix/bad_forecast_spec_behavior branch from 3952168 to c15971f Compare March 23, 2026 22:11
@rma-bryson rma-bryson force-pushed the bugfix/bad_forecast_spec_behavior branch from c15971f to eca6345 Compare March 23, 2026 22:11
@rma-bryson rma-bryson marked this pull request as ready for review March 23, 2026 22:15
@rma-bryson rma-bryson requested a review from adamkorynta March 23, 2026 22:15
@rma-bryson rma-bryson changed the title Workaround to updating forecast location for a spec CDA-98 Workaround to updating forecast location for a spec Mar 23, 2026
});
}

public void updateSpecWithLocationIdChange(ForecastSpec forecastSpec) {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not only update the location id, it updates all fields given your deletes and re-store call.

Additionally, if the location id is the only the thing that needs to be updated, and this is a workaround, direct table edits are much better so you can avoid such destructive calls.

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.

2 participants