Version for persistence data
Posted: Fri Aug 07, 2009 10:26 am
by Carina >> Tue, 7 Oct 2008 12:00:15 GMT
Hallo Jade
I am concerning about dynamic customization schema in Jade.
So far, I can say, Jade has mature features to facilitate this issue ( feature like extract schemas, delta, patch and version ) and really makes every developer (teams) work more intensive and effective.
After time to time, the new idea comes to my head, and I wondering if Jade has another feature to facilitate also this problem.
Here is the scene:
Feature as I enumerate above is only working for schema ( not suitable for persistent data ). I mean that, every changed in schema that we are done is kept very good ( as history ) and transferring schemas between developers in a team are also very simple. Then my question how about keeping history for entry in database ( persistence data ) for very different schema ? ( if our new schema needs new data structure -- or we can say Reorganization Database ). I think, simple backup database is not really enough, because backup process only generate backup data from the current version ( am I am wrong ? ).
At the end .... I am waiting some suggestion
Thanks for any suggestion
Carina
Hallo Jade
I am concerning about dynamic customization schema in Jade.
So far, I can say, Jade has mature features to facilitate this issue ( feature like extract schemas, delta, patch and version ) and really makes every developer (teams) work more intensive and effective.
After time to time, the new idea comes to my head, and I wondering if Jade has another feature to facilitate also this problem.
Here is the scene:
Feature as I enumerate above is only working for schema ( not suitable for persistent data ). I mean that, every changed in schema that we are done is kept very good ( as history ) and transferring schemas between developers in a team are also very simple. Then my question how about keeping history for entry in database ( persistence data ) for very different schema ? ( if our new schema needs new data structure -- or we can say Reorganization Database ). I think, simple backup database is not really enough, because backup process only generate backup data from the current version ( am I am wrong ? ).
At the end .... I am waiting some suggestion
Thanks for any suggestion
Carina