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]
