This document is a great thing to maintain. To make it useful we don't want to include all changes, just the ones (as
Hans wrote) that will require some data updates, and most especially the ones that involve non-backward-compataible data
updates between two revisions.
A PK change is definitely something that needs an upgrade path, and having documentation about how to run the upgrade
service is a great idea.
-David
Jacques Le Roux wrote:
It was a misinterpretation on my side, I thought any change should go
there. Then I asked Bilgin to update.
My domineering tendency was back on this ;o) Sorry for that
Jacques
PS : though maybe having a trace of all changes could be easier than
sometimes poking around :p
From: "Hans Bakker" <[EMAIL PROTECTED]>
If the upgrade does not need any other extra activities then a simple
'svn up', then it is not required to add it too the list.....
to make this document useful the following activities would be nice to
list:
1. A re-load of seed data.
2. A file change which need additional unload/reload/convert activities
3. Any tables which can be deleted(dropped) because they are not used
anymore.
4. Any other required activity to keep your production site operational
On Wed, 2008-08-27 at 02:12 -0700, Bilgin Ibryam wrote:
What should go to this page?
Any data model change or only changes which need additional activities?
In r688993 I added facilityId field to OrderItemShipGroup, but this
change
doesn't require any additions tasks. Should I add this change to the
upgrade
doc?
Bilgin
