Lack of "dirty flag" in Gaedo

[alexblanquart]

As Gaedo does not have the concept of "dirty flag", this implies to change the modeling of certain classes.

class A {
@onetomany(cascade=CascadeType.ALL)
Set list;
}

In this example, we do not have the power on the cascade on the B's side and thus when updating A, it could imply lots of stuff in database to be updated as well even though nothing has changed.

Then, to avoid this behavior, the only way is to model another class C between A and B.