We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Behavior regression introduced in 12.11.5 via #2376
Loading the @onetomany list after refresh() should result in the same SQL-Query as before.
After refresh() the deleted field is ignored.
User user = DB.find(User.class,1); //Before refresh() user.getGroups().forEach(ug->System.out.println(ug.toString())); user.refresh(); //After refresh() user.getGroups().forEach(ug->System.out.println(ug.toString()));
--before refresh() select t0.User_id, t0.id, t0.deleted, t0.User_id, t0.Group_id, from User_Group t0 where ( t0.User_id ) in ( ? ) and t0.deleted = 0; ---------------------------------------------------------------------------------------------------- --after refresh() select t0.User_id, t0.id, t0.deleted, t0.User_id, t0.Group_id, from User_Group t0 where ( t0.User_id ) in ( ? ) ;
The text was updated successfully, but these errors were encountered:
Reference: #2376 ... as the issue that introduced this change in behaviour (and the change we need to adjust in order to fix this issue).
Sorry, something went wrong.
#2581 - SoftDelete on @onetomany is ignored after refresh() (since 12…
febd56c
….11.5)
rbygrave
No branches or pull requests
Behavior regression introduced in 12.11.5 via #2376
Expected behavior
Loading the @onetomany list after refresh() should result in the same SQL-Query as before.
Actual behavior
After refresh() the deleted field is ignored.
Steps to reproduce
The text was updated successfully, but these errors were encountered: