#5610: Useful for dumpdata to be able to use a specific model
-----------------------------+----------------------------------------------
Reporter: DavidReynolds | Owner: DavidReynolds
Status: new | Component: django-admin.py
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 1 | Needs_docs: 1
Needs_tests: 1 | Needs_better_patch: 1
-----------------------------+----------------------------------------------
Changes (by russellm):
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* needs_docs: 0 => 1
Comment:
Replying to [comment:5 DavidReynolds]:
> I'm sure I can fix this, but just wondered what people's opinions were
on whether it needs fixing or not.
Yes, it does :-)
The patch looks essentially ok, except that it needs docs and tests. As
for how to fix the problem you describe - I would suggest collecting the
serialization candidates as a dictionary {app: [model list]}; if you
specify just the app name, the model list is set to None. Each argument
you process checks the existing contents of the dictionary - any existing
None entry means you don't have to add an individual model entry, and if
you process an app but there is already a model list, you can replace the
list with None. (I hope that makes some sort of sense)
--
Ticket URL: <http://code.djangoproject.com/ticket/5610#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
