Opened 18 years ago
Closed 18 years ago
#3380 closed (wontfix)
Add restore/backup action to the admin interface
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Keywords: | admin restore backup db management | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | yes | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
First I'm sorry if there's any error in my submission. I am not used to submit a patch. In fact, it may well be the first time... On the other hand, I'm French so I could have misunderstand points in your guidelines.
My patch add a support for backup in the admin interface. It backups the current objects in the database, for a given table. It uses the cPickle module. It is useful for development server, when you want to add items to your table, and then want to add these writings to your real server, without having to use tools like phpmyadmin, ...
I would be happy if it helps somebody.
Attachments (1)
Change History (5)
by , 18 years ago
Attachment: | patch_django.diff added |
---|
comment:1 by , 18 years ago
Needs tests: | set |
---|---|
Patch needs improvement: | set |
comment:2 by , 18 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
Nice idea, but I think it won't work when your database contains cyclic foreign key dependencies. In the most simple case, when a model has a reference on itself, you're lost, and I doubt that you can fix this unless you put in a *lot* of efforts.
Charlax, take a look at #2333, the part about fixtures is about a similar mechanism (but it's still work in progress).
Patch for adding restore and backup support in the admin interface