#15967: dumpdata and "managed" flag on models
---------------------------------------+----------------------------------
Reporter: ijstokes | Owner: nobody
Type: New feature | Status: closed
Milestone: | Component: Uncategorized
Version: SVN | Severity: Normal
Resolution: duplicate | Keywords: dumpdata managed
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
---------------------------------------+----------------------------------
Comment (by kmtracey):
The documentation for managed
(http://docs.djangoproject.com/en/1.3/ref/models/options/#managed)
explicitly states its only effect is on creation/deletion of tables; I
don't understand where the idea that dumpdata would pay some special
attention to managed=False models and ignore those comes from?
--exclude is also documented for dumpdata:
http://docs.djangoproject.com/en/1.3/ref/django-admin/#dumpdata-appname-
appname-appname-model, though the formatting where some options have
headers and others do not perhaps is obscuring its existence (and that may
be worthy of a ticket). In any case, it is a documented command line flag.
Description of what it supports, exactly, is both in the doc and in the
`manage.py help dumpdata` output, so I don't understand where the idea it
is some undocumented internal feature came from either.
--
Ticket URL: <http://code.djangoproject.com/ticket/15967#comment:2>
Django <https://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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
