#7052: auth fixture fails to import when running test server
------------------------------------+---------------------------------------
Reporter: jb0t | Owner: nobody
Status: new | Milestone:
Component: Serialization | Version: SVN
Resolution: | Keywords: auth_permission
auth_content fixture import
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by russellm):
Replying to [comment:10 shai]:
> I think I have a usable workaround. The idea is simple: Allow each class
to set its own content_type id.
Ok - so what content type should django-tagging use for a tag? How does
the author of django-tagging prevent a clash with the content type for a
blog entry in coltrane?
You have to remember that if you allow/force manual specification of
content types, you have just created a global namespace where clashes are
neither desirable, nor particularly resolvable (since there is no way to
fix clashes without modifying the code for the app). We don't want to have
to resort to the IANA to fix this sort of problem.
--
Ticket URL: <http://code.djangoproject.com/ticket/7052#comment:11>
Django Code <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
