Dear django-devs, I've been reading a lot about the state of dumpdata and loaddata commands in dango. The bug reports that I've found tend to focus improvements to either cosmetic improvements or to a total rewrite of the functionality and pointing discussions to this list.
I've pondered this for a few weeks. Mulled it over. In a fit of foolish bravery, I'm proposing that we look seriously at doing that total rewrite project suggested. Or at least scope it out so we know what it's trying to do for our users. Firstly let's say it's a clean slate, created some different command names. This means it could be handled structurally as a separate project first, maybe moved into contrib later after much vetting. I'd run away and make this now, but I know other django-devs are filled with wisdom and past context, hence my request here for advice before committing to code. I'd like to develop proper user stories, but these are the uses I can think up at the moment: * Test suite fixtures * Site initialization data * Horizontal data sharing (usually chunks of data) * Moving between database types * Backing up data? These are the issues: * No relationship control (missing relationships, no user handling) * No migration state (and no migration for fixtures) * No difference between whole and part data * Default inclusion of auto generate content (permissions, etc) * No rules for handling conflicts, duplication, merging. * No handling for media files (included or linked) * No meta-data about user data handling, licensing or ownership. I won't put together a solution to any of these because I think there's probably some more refinement of the problem first. Please do rip these apart and let me know if you've encountered anything else. Thanks for reading. With Regards, Martin Owens -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/45f6db3904013760b8ba591df96c791bfa5ca5e2.camel%40gmail.com. For more options, visit https://groups.google.com/d/optout.