On 10/09/17 18:41, Mats Wichmann wrote: > restore" and a local copy of the (mysql) db will be built. So that's > what I just agreed with: the setup process happens outside the code app ... > maybe it's not that unusual - any time you need to start with a > reproducible known state of the DB, that would work pretty well; it > would be a disaster for a DB where there were tons of commits, stuff > changed mostly interactively, etc.
Absolutely, I'm talking about getting it up and running, once you start loading live data and making regular changes you are into proper data backups and logging and all the rest of the stuff any good DBA should do in their sleep. Possibly even a hot standby using snapshots/synchronisation technology. But in the early dev/test phase of a project you regularly have to pull down and setup the database and in those cases separate SQL scripts are the best option in my experience. -- Alan G Author of the Learn to Program web site http://www.alan-g.me.uk/ http://www.amazon.com/author/alan_gauld Follow my photo-blog on Flickr at: http://www.flickr.com/photos/alangauldphotos _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: https://mail.python.org/mailman/listinfo/tutor
