hi all,
I was looking at a sourceforge support request (mine, actually, the one
about reply-to on this list)
and a relatively simple means of getting 'entity change histories' to work
within the system occurred to me:
a top-level tag in the entity definition:
<entity:history>true</entity:history>
what would that do?
-When you generate metabase xml schemas, _two_ schemas would be created,
one with the name of the entity: "furbees" and another: "furbees_history"
-furbees_history would contain the same fields as furbees, with the
addition of two important fields:
-history_id
-history_timestamp
With those two tables, it would be _relatively_ easy to implement a
GetByHistory() method in EntityManager, which would trickle down to the
correct Query to furbees_history through QueryManager..
that's easy to deal with for applications like bugtrackers, support
requests, etc...
so you could ask for the 'current copy' of the entity, or one of the copies
by id or timestamp, or all but the current, or all.. etc.
something where you have a set of fields but need to maintain the same key
id.
----
/rant.
_alex
|
