Hey Raymond, Op 11 okt. 2014 21:23 schreef "Raymond Burkholder" <r...@oneunified.net>: > > As a project evolves, database schema changes: tables come and go, columns > come and go, relations come and go. > > In Sqlalchemy, there is a way to track the changes, and create a small > module to apply changes to production as development produces fixed in time > deltas. > > Is there an accepted practice with Wt for creating / managing small modules > to update schema changes without dumping, deleting, creating, and reloading > a database each time?
Currently we keep track of changes in update scripts which we store also in our source repositories. That works in practice but is a hassle especially with identifying which updates are needed. This pain point could be remedied by saving the schema version in a table but we have no concrete plans for this yet. In your mind, does sqlalchemy have the right solution? Koen
------------------------------------------------------------------------------
_______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
