if you look in the test cases there is a contract->version->effectiveness test that shows the classic pattern of effectivity of a business object over time with versions.
This is just the data model, of course, and you would need to manage creation of the versions and effectiveness objects, but that's pretty trivial. -----Original Message----- From: Robert r. Sanders [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 6:24 AM To: OJB Users List Subject: Re: versioning and OJB Depends on what type you mean. I have thought some on the subject of versioning objects and any subobjects; to provide a tag/milestone based versioning. First, it seems to me that this would be a fairly significant project; best built as a module running on top of the OJB core. Second, it the complexity (and DB space) could become very large depending on the number of feature required. Finally, it seems to me, that most of the complexity could be hidden inside of a sufficently sophisticated versioning module that used OJB's metadata to save just the column values that changed, but I am not familiar with the theory behind versioning systems. Anton Komratov wrote: >Are there any thoughts how to implement versioning using OJB? > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Robert r. Sanders Chief Technologist iPOV www.ipov.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
