Although supporting this was a neat idea, this change now requires that I delete the version from any entity I loaded from the database before saving it.

[acuthbert]

Although supporting this was a neat idea, this change now requires that I delete the version from any entity I loaded from the database before saving it.

Which by itself isn't that big of a deal, except in the case where I'm saving an entity without having updated any other fields (from a client request), save() skips the update as it should, which is fine except the same entity with the version removed gets returned.

This can lead to all sort of issues since you expect the entity returned by save() to always represent the information that's in the database.

So now to get the same behavior as before I practically have to re-implement the same mechanism as save() and check if the object was modified before deleting the version from the object and calling save()...

Originally posted by @Malbeth81 in #3271 (comment)