On 4-7-2012 1:13, natasha.ba...@utoronto.ca wrote: > On Tuesday, July 3, 2012 5:55:32 PM UTC-4, ke1g wrote: >> >> In fact, I think dumpdata takes an app name, not a table or model name.
No it doesn't. It can take a app.model name as well and is more commonly used, since the primary use case for dumpdata is to provide seeds for semi-static data, like a categories table. > So maybe my actual question should be why is the category_id many-to-many > field showing up blank consistently when I do a dumpdata?? On 3-7-2012 21:21, natasha.ba...@utoronto.ca wrote: > The table is defined as follows --> id: integer PRIMARY KEY > unipart_id: integer category_id: integer This misses a unique index on (unipart_id, category_id) but doesn't explain the issues you're seeing. Any chance we can see the actual models and one broken record as outputted by dumpdata? -- Melvyn Sopacua -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
