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).
-
Steve Ebersole
Project Lead
http://hibernate.org
steve(a)hibernate.org
Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.com
steve.ebersole(a)jboss.com
steve.ebersole(a)redhat.com
On Mon, 2008-10-27 at 10:09 +0100, Max Rydahl Andersen wrote:
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,
> as every programmer
> has some knowleger of version tracking ( I hope for them at least).
>
> @KeepVersions @TrackVersions @VersioningControlled ?
>
> 2008/10/25 Elias Ross <genman(a)noderunner.net>:
>> On Fri, Oct 24, 2008 at 5:00 PM, Emmanuel Bernard
>> <emmanuel(a)hibernate.org> wrote:
>>> @StoreHistory
>>> @KeepHistory
>>>
>>> I probably like @Audited better though.
>>
>> @Historized sounds computer science-y and pretty cool. @Chronicled is
>> also pretty cool sounding.
>>
>> "Audit" is right out. It means: "1 a: a formal examination of an
>> organization's or individual's accounts or financial situation b: the
>> final report of an audit 2: a methodical examination and review" ..
>> You're not examining anything, really you're remembering.
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev