Skip to content
This repository has been archived by the owner on Nov 7, 2020. It is now read-only.

Duplicate key constraint when multiple requests try to populate same item #86

Open
mentos1386 opened this issue Jan 25, 2018 · 1 comment

Comments

@mentos1386
Copy link
Member

When doing same request at the same time, with empty database. One of them will fail with duplicate key constraint. As both of them try to populate entety from esi to db. We should handle key constraint and try to fetch entity from database again (as now it is populated and we don't have to).

@mentos1386 mentos1386 added this to the Alpha milestone Jan 25, 2018
@mentos1386 mentos1386 self-assigned this Mar 12, 2018
@mentos1386 mentos1386 removed their assignment Mar 12, 2018
@mentos1386 mentos1386 added this to Ready for development in New Eden Social Jun 30, 2019
@mentos1386 mentos1386 moved this from Ready for development to Next in New Eden Social Sep 5, 2019
@mentos1386
Copy link
Member Author

When #126 is done, we should reevaluate if this is even going to happen, as we don't populate entities the same way anymore.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

1 participant