Skip to content

fix(db-mongodb): documentDB unique constraint throws incorrect error #4513

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

Merged
merged 1 commit into from
Dec 19, 2023

Conversation

DanRibbens
Copy link
Contributor

Description

fixes #4460

  • I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have added tests that prove my fix is effective or that my feature works
  • Existing test suite passes locally with my changes
  • I have made corresponding changes to the documentation

@DanRibbens DanRibbens force-pushed the fix/#4460-documentdb-unique-error branch from 9b05fd5 to b530f71 Compare December 14, 2023 21:45
@DanRibbens DanRibbens merged commit 05e8914 into main Dec 19, 2023
@DanRibbens DanRibbens deleted the fix/#4460-documentdb-unique-error branch December 19, 2023 19:14
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.

DocumentDB unique error does not have keyValue in Error object, generic error shown
1 participant