Also consider: the “safer” default strategy might require full reflective access to all fields/properties - we need to ensure that’s possible in Quarkus.

A better alternative would be to check if there’s any field set to the default value, and in that case just consider the entity dirty. That’s not optimal, but it’s only happening on re-attaching of an unmanaged entity - which is not something we’d recommend doing to begin with.