Some changes I will be making to our version of django after the New
Year's. I'm interested on everyones opinions if I should make them
compatible w/ development Django and submit them.

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

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

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.

If anyone has any criticism as to why these are bad ideas, or if its
already in the works, let me know so I can save some time


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to