Hello,
One thing I would like to see in adition is the ability to store
flattened audting of changes. There are many examples of such a thing
on the wiki and the web at large.
yes, that's one of the points on my roadmap - "support for different
versioning schemes" (provided I have the time to
I think the "plug in the way versioned data is stored" bit accounts for
what I meant :)
Also I suggest that you move away from the term "versioning" here. This
is already:
1) over-used/over-loaded
2) used by the JPA spec to mean optimistic locking.
Really this is "auditing" or "capturing histori
Guys,
This is the one which originated the changes in the parent Test class for
Entity Manager, but somehow we managed to forget it :-) So, after discussing
the approaches, I did a new diff to replace the old one, which uses the
parent's capabilities on handling the sessions and exceptions.
N
I have done a pass to make the APIs and internals more typesafe
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-282
Mainly starting using . There is probably a lot of areas where it's
missing.
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-281
It mean I di
I can see the confusion. Hibernate has a similar annotation for
optimistic locking which nearly matches "Versioned" in Envers.
Some "Version"-free class naming ideas:
RevisionListener
VersionsReader -> RevisionReader | HistoryReader
Classes
DefaultRevisionEntity
VersionsReaderFactory -> RevisionR
I wonder if it really has to be a project on its own?
A module in core would make more sense?
--
Emmanuel Bernard
http://in.relation.to/Bloggers/Emmanuel | http://blog.emmanuelbernard.com
| http://twitter.com/emmanuelbernard
Hibernate Search in Action (http://is.gd/Dl1)
On Oct 21, 2008, at 1
