On 12/23/06 6:31 AM, [EMAIL PROTECTED] wrote:
1. 2 extra arguments on select_related: depth, the depth of related tables it will query for; keys, a list of fields [relational keys] to limit the joining of
This would be extremely useful; I'd love it if you'd work up a patch for that.
2. content types being added to ._meta. We use them all the time and I don't like querying or hitting the cache just to get the "ID" of my model. The plan would be to have these saved at runtime and updated using signals
This has been discussed before; search the ticket tracker before you start on anything.
3. generic relations, that are useful. I dont know if they've become useful since before, but when I first tried them they didnt help me much. The idea is a you have 2 fields, such as content_type, and object_id, and another field called, lets say my_table_name. my_table_name = TrueGenericRelationThing(content_type, object_id). You would be able to then reference htis just like a normal ManyToMany or ForeignKey field.
These already exist: http://www.djangoproject.com/documentation/models/generic_relations/
Jacob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
