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 command, and that still suffers from the need to re-write at schema changes. On Wed, Mar 9, 2016 at 6:24 PM, Mike Dewhirst <mi...@dewhirst.com.au> wrote: > 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 presume this is a Postgres scripting task or is there a Django recipe? > > Thanks for any pointers > > Mike > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/56E0B0A1.6000809%40dewhirst.com.au > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAB%2BAj0szPfR5KZM32R6EePgf%3D9B4gw-gnty2-yNO2O7AWCZG7Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
