Added ticket http://code.djangoproject.com/ticket/6155 with patch.
Still need to write tests.
Michael
On Dec 7, 2007 3:15 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
>
> On Dec 7, 2007 2:31 PM, Empty <[EMAIL PROTECTED]> wrote:
>
>
> >
> >
> > > Seems dumpdata is coded to require a Manager named
On Dec 7, 2007 2:31 PM, Empty <[EMAIL PROTECTED]> wrote:
>
> > Seems dumpdata is coded to require a Manager named 'objects' for the
> Models
> > it dumps, even though (as described here:
> > http://www.djangoproject.com/documentation/model-api/#manager-names),
> Django
> > does not require that a
> Seems dumpdata is coded to require a Manager named 'objects' for the Models
> it dumps, even though (as described here:
> http://www.djangoproject.com/documentation/model-api/#manager-names), Django
> does not require that a Manager named objects exists for all Models.
> Whether this is just an
On Dec 6, 2007 8:01 PM, ttk <[EMAIL PROTECTED]> wrote:
>
> I think I found my problem...
>
> I failed to add "objects = models.Manager()" into my models which
> would explain why that attribute isn't found.
>
> I'll try this out but if anyone has additional suggestions, I'm all
> ears.
Seems
I think I found my problem...
I failed to add "objects = models.Manager()" into my models which
would explain why that attribute isn't found.
I'll try this out but if anyone has additional suggestions, I'm all
ears.
cheers,
-ttk
--~--~-~--~~~---~--~~
You
Hello all,
I'm getting an attribute error when I try running the dumpdata command
on any of my apps.
news = app name
NewsEntry = model
Output:
=
C:\someproject>manage.py dumpdata news
Traceback (most recent call last):
File "C:\someproject\manage.py", line 11, in
6 matches
Mail list logo
