-
Notifications
You must be signed in to change notification settings - Fork 353
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
@Sequence Annotation generates a new Id on update #2003
Comments
mipo256
added a commit
to mipo256/spring-data-relational
that referenced
this issue
Mar 4, 2025
…n UPDATE queries
mipo256
added a commit
to mipo256/spring-data-relational
that referenced
this issue
Mar 4, 2025
…n UPDATE queries Signed-off-by: mipo256 <[email protected]>
mipo256
added a commit
to mipo256/spring-data-relational
that referenced
this issue
Mar 7, 2025
…n UPDATE queries Signed-off-by: mipo256 <[email protected]>
mipo256
added a commit
to mipo256/spring-data-relational
that referenced
this issue
Mar 19, 2025
…n UPDATE queries Signed-off-by: mipo256 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: spring-data-jdbc:3.5.0-M1
Currently when using the
@Sequence
annotation in an entity, it seems to generate a new value on each save.This results in an error, when trying to update an entity complaining that the newly generated id is not available in the database.
I think there should be a check, so it only generates a new value, when there is none set.
The text was updated successfully, but these errors were encountered: