Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #26041 > unrolled thread

Dumping all the sql statements as backup

Started byandrea crotti <andrea.crotti.0@gmail.com>
First post2012-07-25 14:56 +0100
Last post2012-07-25 14:56 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python


Contents

  Dumping all the sql statements as backup andrea crotti <andrea.crotti.0@gmail.com> - 2012-07-25 14:56 +0100

#26041 — Dumping all the sql statements as backup

Fromandrea crotti <andrea.crotti.0@gmail.com>
Date2012-07-25 14:56 +0100
SubjectDumping all the sql statements as backup
Message-ID<mailman.2572.1343224604.4697.python-list@python.org>
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

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web