View post: What data should be stored in versions tables? - a poll
Navigation
Recent posts from all feeds
- Mobicents JAIN-SLEE Server 1.2.0.CR2 released!<br…
- JSFUnit Beta 3 is out. Seam support and more!
- Netty reaches 75%+ test coverage. What's next?
- Tab Sweep : JBoss
- And now, something slightly different
- DZone Introduction to AOP article
- Updates on JBM 2.0 progress
- Revue de Presse
- Red Hat IT Switches to JBoss EAP 4.3!
- Please stand clear of the closing doors, this train is ready to depart - Seam 2.1.0.BETA1 released!
- « Back to feed: Blog of Adam Warski
What data should be stored in versions tables? - a poll
Hello,
I’ve posted a poll on what data should be stored in versions tables in Envers, see here and cast your vote:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136764
The results will determine the future implementation, so votes really count. And as always, comments & ideas are very welcome.
The two options, in short, are:
- Store only historical data in the versions table, making queries poorer and more difficult (you always have to combine data from two sources - the versions and “current” tables)
- Store all data in the versions table, making queries easier and more powerful. This however duplicates the “current” data.
Adam
Post to DZone
Post to del.icio.us
Digg this!
Stumble It!