On Sep 25, 8:02 am, tWoolie <[email protected]> wrote: > I never saw that ticket. I've been looking at it purely from the > perspective of trying to inject it into the model in my app to get > around doing expensive filtering in my template. > I see Jacob's point that saving a few chars in python is not worth it > for the cost of having to read docs to figure out what it does, but > this would be a fantastic thing to have in templates where there is no > way to specify filtering.
Hello, I believe for this purpose, the Proxy models feature would be the perfect solution, please see: https://docs.djangoproject.com/en/1.3/topics/db/models/#proxy-models -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
