Hi
I found I could use x.extra(select) statements to add custom row's to
my objects, and since this lowers the amounts of query I need immensly,
I've started to love it. (my old front page took about 2 seconds to
load fully, the new one is instant).
Example:
query = query.extra(select={'files_total':'SELECT COUNT(*) FROM
content_filename WHERE content_id=content_content.id'},)
Now this works extreamly well, I can access object.files_total, and
I've made it one big query, instead of doing it in my template (meaning
one query per time I count files).
The problem is, I can't use filters obviusly, as it looks in the model
and fails to resolve "files_total", so I use an extra like this:
query = query.extra(where='files_total > 50')
And this works very well as well, except from when I try to use .count
(or, any other django object tries to, which is breaking paginator for
me right now), as django is "clever" and strips off the select query,
ending up with this:
SELECT COUNT(*) FROM "content_content" where files_total > 1;
Which obviusly isn't going to work. Is there any "offical" way of
adding custom row's?
(note that the actual model is much more advanced, and so are the extra
row's, I'm actually pulling extra row's for "files_total",
"files_checked (which is per user)" and "percentage_checked",
calculated based on the two previus parameters.)
Any help would be very welcome.
Anders Aagaard
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
