On Wed, 2007-01-31 at 17:41 -0800, Rob Hudson wrote:
> > Keep in mind that django.contrib.contenttypes gets installed by
> > default, and is used by the comments app, the auth app, the admin app
> > and the generic relations framework.
> >
> > It's hard to escape it :)
>
> I quickly grepped the docs directory and it's not mentioned that you
> can't have a model named "ContentType". If Django wants this to be a
> reserved model name, then at the least this thread can result in
> documenting that.
>
> But it's just a model name... Django doesn't break if you have an app
> with a model name of "Car", and another app with a model name of "Car".
> It's pretty good at keeping the models separated by app. I took at look
> at django.db.models.loading from the shell and it's keeping everything
> straight and tidy as a list of:
>
> {'app': 'model1', 'model2', ... }
>
> I guess I thought that this would be a straight forward fix for someone
> who knows the ins and outs of the ORM well -- a special case buried
> somewhere.
So after some back and forth about whether this should or shouldn't
work, there didn't seem to be any resolution. Your gut feeling looks
right to me Rob: it should probably work as you expect (no collision),
although it won't surprise me if it doesn't (because ContentTypes are
mixed into generic relations, which is part of core still).
I'll have a look at this, since I've delved into models.loading a lot in
the past (and intend to do so again in the near future).
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
