On 7/25/2012 8:56 AM, andrea crotti wrote:
I have some long running processes that do very long simulations which at the end need to write things on a database.At the moment sometimes there are network problems and we end up with half the data on the database. The half-data problem is probably solved easily with sessions and sqlalchemy (a db-transaction), but still we would like to be able to keep a backup SQL file in case something goes badly wrong and we want to re-run it manually.. This might also be useful if we have to rollback the db for some reasons to a previous day and we don't want to re-run the simulations.. Anyone did something similar? It would be nice to do something like: with CachedDatabase('backup.sql'): # do all your things
I'm now starting to do something similar, but in C, not Python. Apparently not using SQL. The simulations this is for often last a month or more. -- http://mail.python.org/mailman/listinfo/python-list
