Closed RualSepp closed 2 years ago
Behavior regression introduced in 12.11.5 via https://github.com/ebean-orm/ebean/issues/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 ( ? ) ;
Reference: https://github.com/ebean-orm/ebean/issues/2376 ... as the issue that introduced this change in behaviour (and the change we need to adjust in order to fix this issue).
Behavior regression introduced in 12.11.5 via https://github.com/ebean-orm/ebean/issues/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