Fix constraint violation in Jobset update #576
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Until now I usually get an error like this when I try to update a jobset configuration which contains several inputs: ``` DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::SQLite::st execute failed: UNIQUE constraint failed: JobsetInputAlts.project, JobsetInputAlts.jobset, JobsetInputAlts.input, JobsetInputAlts.altnr [for Statement "INSERT INTO JobsetInputAlts ( altnr, input, jobset, project, value) VALUES ( ?, ?, ?, ?, ? )" with ParamValues: 1=0, 2='github', 3='baumal', 4='alarm', 5='https://github.com/nixos/nixpkgs'] at /home/ma27/Projects/hydra/src/script/../lib/Hydra/Controller/Jobset.pm line 279 ``` This happens to occur since the table `JobsetInputAlts` contains a primary key over the fields `project`, `jobset`, `input, `altnr`. When I alter another value (e.g. switching the state from "Enabled" to "Disabled") the controller tries to create a new input which collides the the primary key declaration. To work around this, the database should check first if the input already exists by using `update_or_create`.
|
I can't reproduce the issues on latest Hydra anymore -> closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Until now I usually get an error like this when I try to update a jobset
configuration which contains several inputs:
This happens to occur since the table
JobsetInputAltscontains aprimary key over the fields
project,jobset,input,altnr`. When Ialter another value (e.g. switching the state from "Enabled" to
"Disabled") the controller tries to create a new input which collides
the the primary key declaration.
To work around this, the database should check first if the input
already exists by using
update_or_create.