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

Fixed handling of DuplicateKeyException errors after crate-python 0.34 #439

Merged
merged 1 commit into from
Apr 24, 2024

Conversation

amotl
Copy link
Member

@amotl amotl commented Apr 24, 2024

Problem

Thanks for reporting, @romseygeek and @proddata.

Details

After an improvement in crate-python 0.34, this error case is conveyed through IntegrityError. Beforehand, a more generic ProgrammingError was used.

Without the update, a duplicate key exception causes crash to exit prematurely and unexpectedly, when using more recent versions of crate-python.

Solution

Now, both exception types will be handled in the same way.

@amotl amotl requested review from seut and matriv April 24, 2024 17:53
After an improvement in crate-python 0.34, this error case is conveyed
through `IntegrityError`. Beforehand, a more generic `ProgrammingError`
was used.

Without the update, a duplicate key exception causes crash to exit
prematurely and unexpectedly, when using more recent versions of
crate-python.

Now, both exception types will be handled in the same way.
@amotl amotl force-pushed the amo/handle-integrity-error branch from e639940 to 3306eff Compare April 24, 2024 17:57
@amotl amotl marked this pull request as ready for review April 24, 2024 17:58
@amotl amotl merged commit 905e8dc into master Apr 24, 2024
21 checks passed
@amotl amotl deleted the amo/handle-integrity-error branch April 24, 2024 18:43
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