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 du
Hm, I think the functionality to do this -- at least if I understand
correctly what I read
here:
http://stackoverflow.com/questions/1113096/django-dump-data-for-a-single-model
I'd be fine dumping the data for the entire app -- but the reason I did it
this way is because when I do this, the cat
In fact, I think dumpdata takes an app name, not a table or model name.
On Tue, Jul 3, 2012 at 5:54 PM, Bill Freeman wrote:
> I think that you have to dumdata one or both of the models at the ends
> of the many to many,
> and the join table will come along for free.
>
> On Tue, Jul 3, 2012 at 3:2
I think that you have to dumdata one or both of the models at the ends
of the many to many,
and the join table will come along for free.
On Tue, Jul 3, 2012 at 3:21 PM, natasha.ba...@utoronto.ca
wrote:
> Hi All,
>
> I'm trying to dump the contents of a table which is the mapping for a
> many-to-m
Hi All,
I'm trying to dump the contents of a table which is the mapping for a
many-to-many field.
The table is called Part and it has a ManytoManyField called
category_id.
When I run python manage.py dumpdata store.part_category_id >
file.json
I get the error Error: Unable to serialize database
5 matches
Mail list logo
