arthur debert wrote:
> ps: how is the GenericForeignKey going to work? will it be imported > from the tagging app's package, or will it go into trunk? There is no guarantee that any of this stuff will go into trunk at all - the core django devs would obviously have to be for it first. But the GenericForeignKey class could be usefully part of the ContentTypes contrib app. However, one constraint of my current project is that I have models with string primary keys. I've got a simple 'mapper' system for dealing with this that GenericForeignKey uses, but I'm not sure if it is such a common case that it is worth the extra hassle - for example, the 'comments' contrib app does not handle this case AFAICS. Perhaps GenericForeignKeyInteger and GenericForeignKeyString could both be created - looking at the 'comments' contrib model, GenericForeignKeyInteger could be used to improve it - it would replace (or augment) the get_content_object() getter method with an attribute that handles both setting and getting. Luke --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
