[OSSTEST PATCH 03/17] schema updates: Document how to remove a used column

[Ian Jackson <ian.jackson@eu.citrix.com>]

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
 schema/README.updates | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/schema/README.updates b/schema/README.updates
index c5abc36..ca1d37e 100644
--- a/schema/README.updates
+++ b/schema/README.updates
@@ -147,6 +147,32 @@ finish is needed', this will usually involve passing an appropriate
 `-o' option.
 
 
+Update order for Cleanup
+------------------------
+
+This is for when we want to get rid of some old information in the
+database.  Sometimes the information will have been replaced eg via
+a Populate-then-Rely change, as described above.
+
+There are typically two schema changes:
+
+* To allow the new information to be left blank (eg for the column to
+  be NULL).  Call this `unconstrain'; it is an `Explicit conditional'
+  change.
+
+* To drop the information entirely.  I will call this `drop'.
+  It is `Code first'.
+
+1. Commit: new schema updates `unconstrain', status `Unfinished'
+   and `drop', status `Unfinished'.
+
+2. Commit code which tolerates the information being missing;
+   changing `unconstrain' to Ready.
+
+3. Commit code which no longer writes the information; changing
+   `unconstrain' to Needed and `drop' to Ready.
+
+
 Statuses and rules for push and db update
 -----------------------------------------
 
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel