On Mon, Dec 15, 2008 at 11:24 AM, Mark <[email protected]> wrote: > > Hello, > > Are there any comments on the issue I describe below? > Aside from issue 7052 in the tracker: > > http://code.djangoproject.com/ticket/7052 > > I'm a new user of Django so I may be doing something > wrong.
You're not doing anything wrong. The issue you are describing here isn't a new issue, either - it is exactly what #7052 is describing. Regarding your proposed solution - I'm sure it works, but it's not the right solution. The problem you have observed with content_types is part of a much larger problem. Ticket #7052, for example, highlights that the same problem exists with Permission objects in the auth contrib app. The larger problem is the serialization of content that is dynamically created as a result of a post_syncdb trigger. The solution here isn't to make a special case of content_type (or any other affected type). The solution is to find a reliable way to serialize dynamically created content. The ticket for #7052 describes one possible solution - modifying the serializers so that they can dynamically query for content that is known to be dynamically reated. Suggestions for other solutions are welcome, but keep in mind that they must be general solutions for the problem (not making special cases of content_type or any other data type), and they must be backwards compatible. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
