http://migratosaur.dev.java.net
Nothing fancy about it, but it is maintained and works well for me =) No automated schema change discovery and guesswork -- no way to *know* the intention of changes, unfortunately. Any migration requires some human integration.
I can imagine a "database refactoring browser" with a drag/click-and-act/etc type thing which encapsulates the actions into a serializable thing to automate this, but to my knowledge no one has written one.
-Brian
On Sep 21, 2004, at 5:57 PM, Ajitesh Das wrote:
Reposting again. Let's see if anybody has any recommendation.
-----Original Message----- Hi List: I like to know if anybody who uses OJB platform in his product has done anything on object model migration. This seems to be a missing piece in OJB project. Am I missing something? Example Scenario: I have an existing application that uses OJB as OR platform contains a set of business objects. In this new release, we are altering the definition of business object by adding new fields for some objects and deleting some fields for others. I would like to know how other users are handling the two situations: (a) When you add a new field to an existing object and (b) when you delete a field in an existing object. So that the old data can be kept and properly defaulted.
I have searched the Wiki ,docs and mail archive but could not find any recommendation/reference from the OJB developers/gurus or reference to some design patterns.
Regds Ajitesh
--------------------------------------------------------------------- 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]
