Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Character Blueprints not checking if blueprint already exists on another character #828

Closed
Dusty-Meg opened this issue Aug 31, 2021 · 0 comments · Fixed by eveseat/eveapi#310

Comments

@Dusty-Meg
Copy link

Dusty-Meg commented Aug 31, 2021

  • Problem:
    Character blueprints endpoint failing due to Integrity constraint violation: 1062 Duplicate entry
    This looks to be due to the blueprint item_id already existing in the database but under a different character.
    I checked the blueprint that has been throwing one of the errors and it was a blueprint that I had contracted between characters.
    Guessing it is trying to add the blueprint into the database before removing it from the previous character.

  • Expected:
    Blueprints job succeeds and updates all characters blueprints

  • Logs / Screenshots / Proof:
    PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '1036646390848' for key 'PRIMARY' in /var/www/seat/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:112

  • Version Info:
    Docker install.
    +--------------------+---------------+----------------+
    | Package Name | Local Version | Latest Version |
    +--------------------+---------------+----------------+
    | SeAT API | 4.6.0 | 4.6.0 |
    | SeAT Console | 4.8.0 | 4.8.0 |
    | SeAT Eve API | 4.13.1 | 4.13.1 |
    | SeAT Notifications | 4.3.1 | 4.3.1 |
    | SeAT Services | 4.2.0 | 4.2.0 |
    | SeAT Web | 4.14.1 | 4.14.2 |
    +--------------------+---------------+----------------+

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 a pull request may close this issue.

1 participant