On 7 September 2011 12:43, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
A specific interface is what looks the best to me too.
#2 we might be able to reuse #1's interface.
I don't fully understand what allowSkipOnUnchangedFields does.
I think we need a way for implementors to state that the index needs
to be updated even if all the listed properties are not considered
dirty, basically a toggle to disable the optimisation for a specific
Example: when the entity is updated, and no indexed fields are
changed, but we still want to store a "last updated timestamp" in the
If you think we don't need it I'll be glad to leave it out.