-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 5 posts ] 
Author Message
 Post subject: Hibernate based Object Version Management
PostPosted: Wed Oct 25, 2006 2:20 pm 
Newbie

Joined: Wed Oct 25, 2006 2:12 pm
Posts: 6
Hi,

I'm wondering if somebody know an existing framework allowing to version control objects stored in DB and to allows functions such as:
- baseline
- branch
- checkin
- checkout
- revise
- ...


If no tool exists, I'm wondering what is the best solution... I'm planning to somehow *tag* the versionable objects. In that case, the hibernate mapping of the object will be cut in 2 tables:
- Master : stores the object unique reference
- Slave : stores the version dependents object

Then the DAO will have to handle the above listed functions and the pojo objects must unify the master/slave transparently to user.

I still have no idea how to implement that neither how to *automate* it based on a *tag on the pojo*.



I would be glad to ear any comment / suggestion / lead ....
Thks for your help.


Top
 Profile  
 
 Post subject: Triggers would do this
PostPosted: Wed Oct 25, 2006 4:29 pm 
Newbie

Joined: Wed Oct 25, 2006 9:27 am
Posts: 3
Location: Poland
Have you considered triggers?

They run on a databse level, that means that they are: fast, reliable, client agnostic. Of course, with complex OR mappings maintainig such triggers would be difficult. But the performance would be always much better than with middle tier solutions.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Oct 26, 2006 9:16 am 
Newbie

Joined: Wed Oct 25, 2006 2:12 pm
Posts: 6
I did considered triggers.

Problems with trigger are:
- Protability : I expect my application to be available on several databases with minimum customisation
- Triggers can automate the creation of new version but when you reach to checkin / checkout / retrieve a baseline, it requires a user interaction and therefore it must be handled through the dataaccess layer...


Top
 Profile  
 
 Post subject:
PostPosted: Sun Oct 29, 2006 3:14 am 
Newbie

Joined: Wed Oct 25, 2006 2:12 pm
Posts: 6
Does hibernate inheritance mapping have to match pojo's inheritance ?


Top
 Profile  
 
 Post subject:
PostPosted: Thu Nov 02, 2006 11:23 am 
Beginner
Beginner

Joined: Thu Nov 02, 2006 9:38 am
Posts: 32
Location: Belgium
Look at subversion's model for versioning, it has a very powerful approach to tagging. But that doesn't really answer your question.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 5 posts ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.