I like @TrackHistory
/max
@KeepHistory sounds well, it's straightforward to what it's going to do.
I was thinking about @TrackChanges but you aren't really building
"diff"s,
so "history": @TrackHistory or @KeepHistory ?
still including some flavour of the "version" should be better IMHO,
a
Generally annotations on an entity are describing a quality of the
entity, whereas a lot of these suggestions are describing actions to be
done with or on behalf of the entity (e.g., its @Entity not
@StoreInDatabase, its @Version not @UseToOptimisticlyLock, its @Id not
@TrackIdentifierValue, etc).
The term 'audit' here is fairly well excepted in our field to mean
exactly what we are talking about here.
And besides, you cant use the dictionary to dismiss one possibility in
favor of another that does not even exist in the dictionary ;)
-
Steve Ebersole
Project Lead
http://hibernate.org
I know, but I still like it ;)
/max
Generally annotations on an entity are describing a quality of the
entity, whereas a lot of these suggestions are describing actions to be
done with or on behalf of the entity (e.g., its @Entity not
@StoreInDatabase, its @Version not @UseToOptimisticlyLock, i
This performance and stability focused beta is out
http://in.relation.to/Bloggers/HibernateSearch310Beta2FocusOnLockContention
Special thanks to Sanne for all the work on the Lucene backend.
CR1 is planned mid-november-ish with a GA following shortly.
The CR will contains some additional Lucene
