I've mostly done the work for splitting data migrations out into
individual scripts for each schema version and automating this process
using sqlalchemy-migrate. I hope to get this committed soon.

Surprisingly, Pytrainer used to have a rudimentary version-by-version
upgrade mechanism. In revision 480 dgranda discarded this upgrade
mechanism and all the upgrade scripts for previous versions and
introduced the current DB schema numbering system - so the current DB
numbering system actually only dates back to version 1.7.0. I will
assume we are not interested in restoring migration paths from older
versions and use the 1.7.0 schema as the initial schema for the
upgrade sequence.

 - Nathan

------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Pytrainer-devel mailing list
Pytrainer-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pytrainer-devel

Reply via email to