[Treebase-guts] SF.net SVN: treebase:[483] trunk/treebase-core

[<vga...@us...>]

Revision: 483
          http://treebase.svn.sourceforge.net/treebase/?rev=483&view=rev
Author:   vgapeyev
Date:     2010-02-04 17:46:20 +0000 (Thu, 04 Feb 2010)

Log Message:
-----------
Adding the dir that will be set up to keep track of DB schema snapshots and patches. 

Added Paths:
-----------
    trunk/treebase-core/db/
    trunk/treebase-core/db/README.txt
    trunk/treebase-core/db/TODO.txt

Added: trunk/treebase-core/db/README.txt
===================================================================
--- trunk/treebase-core/db/README.txt	                        (rev 0)
+++ trunk/treebase-core/db/README.txt	2010-02-04 17:46:20 UTC (rev 483)
@@ -0,0 +1,30 @@
+[This will contain instructions on how to do and commit patches. 
+For now, it's just a message from my email 2010-02-03  --VG]
+
+"A setup/discipline for schema changes"
+
+This brings up something that was on my back burner for a while:  
+setting up a workflow and a file/directory structure to maintain  
+schema patches. That would be something similar to migration scripts  
+in Ruby or Python (but with scripts written in SQL and no automation).
+
+The idea is that we store in SVN the initial snapshot of the DB schema  
+and sequential parches that we have been developing w.r.t  
+treebasedev.  These patches will be used to bring up-to-date  
+treebasestage, and then treebaseprod.   After that we can erase the  
+patches, refresh the snapshot, and continue for another cycle.   
+Official TB2 code releases are to be declared at the start of a cycle,  
+when there are no patches yet.  The snapshot is what should be used to  
+create a fresh TB2 instance.
+
+I suggest to create the directory treebase-code/db to store patches  
+and snapshots.  (Another option would be a separate project, treebase- 
+db, a a sibling of treebase-core and treebase-web.)
+
+Patches are to be sequentially numbered (by hand).  To keep track  
+which DB instance has already been brought up to which patch version,  
+I suggest creating a special table with a number column.  Each patch  
+will have an UPDATE setting the number in the table to the patch's  
+number.
+
+If this sounds ok, I hope to set this up by end of tomorrow.

Added: trunk/treebase-core/db/TODO.txt
===================================================================
--- trunk/treebase-core/db/TODO.txt	                        (rev 0)
+++ trunk/treebase-core/db/TODO.txt	2010-02-04 17:46:20 UTC (rev 483)
@@ -0,0 +1,7 @@
+Pending schema patches: 
+
+[To be put in as patches after the storage structure for them is in place in this directory -- VG 2010-02-04]:
+
+* Drop geospot_id_sequence -- there is no corresponding sequence
+* Correct PK name in stepmatrixelement and create stepmatrixelement_id_sequence
+* Create indexes, as suggested by Bill 2010-02-03 (and maybe later)


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.