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

Add new error for "Violation Check Constraint" #271

Merged
merged 4 commits into from May 8, 2024

Conversation

anilsenay
Copy link
Contributor

  • Do only one thing
  • Non breaking API changes
  • Tested

What did this pull request do?

Added 23514 pgerrcode support

User Case Description

Detailed here: go-gorm/gorm#6992

@anilsenay
Copy link
Contributor Author

anilsenay commented Apr 25, 2024

This PR requires to merging go-gorm/gorm#6992
After go-gorm/gorm#6992 merged and released a new version, this pr must be updated

@anilsenay
Copy link
Contributor Author

hey @jinzhu can you take a look?

@anilsenay
Copy link
Contributor Author

hey @jinzhu can you take a look?

+up

(sorry for bothering you but I want to use this feature in my project 😄)

Copy link
Member

@a631807682 a631807682 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anilsenay
Copy link
Contributor Author

Can we add the doc link in comment? like mysql

https://www.postgresql.org/docs/current/errcodes-appendix.html

done 👍

@a631807682 a631807682 merged commit d1db251 into go-gorm:master May 8, 2024
1 check passed
@anilsenay
Copy link
Contributor Author

anilsenay commented May 8, 2024

@a631807682 if there is no pr to merge, could you create new tag as v1.5.8 👉 👈

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.

None yet

2 participants