That's a good question. I'd rather write it in python, but if it runs
daily on non-trivial tables, I suspect that performance is better with a
script that gets the DB to produce the dump files, maybe onto a NAS. The
restore part should be a lot less frequent, so performance is probably less
impor
On 10/03/2016 11:15 AM, Bill Freeman wrote:
The only problem I can think of with a DB script is that it may have to
be recoded at unpleasant times, such as when you run a migration to take
a new version with a security fix.
If you are going to do it in Django, it would be by saving stuff out to
The only problem I can think of with a DB script is that it may have to be
recoded at unpleasant times, such as when you run a migration to take a new
version with a security fix.
If you are going to do it in Django, it would be by saving stuff out to a
fixture, maybe with a custom management comm
I have a Django project oriented around lots of companies and each
company enters its own data. I need to produce a separate individual
database backup or dump for each company.
It will be used on request to perform an individual restoration after
user error has damaged a company's data.
I p
4 matches
Mail list logo
