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 15:09, Steve Ebersole wrote:
I'd say yes most definitely...
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.
-
Steve Ebersole
Project Lead
http://hibernate.org
[EMAIL PROTECTED]
Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.com
[EMAIL PROTECTED]
[EMAIL PROTECTED]
On Tue, 2008-10-21 at 20:41 +0200, Adam Warski wrote:
But, as the logical place to do this would be in hibernate, this
brings the question: would you (= the Hibernate team) be interested
in Envers and in me developing it further? :)
I'll take the lack of answers as a no :) But thanks, Max and Sanne :)
Meanwhile, maybe it will interest some of you, I've just released
Envers 1.1.0.GA. The main new features are the possibility to version
most types of relations and persistent collections and an improved
revisions-of-entities query; you can now read the history of an
entity
along with revisions metadata in a single query.
More details on the blog: http://www.warski.org/blog/?p=20 and the
website: http://www.jboss.org/envers/
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
