From: "David E. Jones" <[EMAIL PROTECTED]>
We definitely need to discuss this more...
The main thing to consider when updating is entities with primary key changes, which should ALWAYS be done by
deprecating the current entity and creating a new one, and creating a service to move the data from the old entity to
the new one. There is really no excuse for not doing so, and while I've reminded people about it a few times I'm tempted
to start reverting commits if people don't do this. Yes, it's that important. Saying that someone should do this
manually through an export and import is a bad idea and a real PITA, even with separate old and new entities.
+1
As for seed data: the way "seed data" is defined and used means that it should ALWAYS be reloaded when updating an
existing system. The pattern and how and such is pretty well explained in the ofbiz/build.xml file.
+1
Also, there are lots of things that people can do when updating, but don't really have to. Removing unused tables is a
good example of this. Usually server capacity is way cheaper than human time.
+1
Ready for discussion :o)
Jacques
-David
Hans Bakker wrote:
I created a first version of a OFBiz system upgrade document.
any comments welcome.....
http://docs.ofbiz.org/display/OFBTECH/Upgrading+OFBiz+from+earlier
+revisions
