I don't know why it was decided only object methods should be called. I'm
waiting for the review of the patch.
Regards
QuearySets are lazy and, as I understand it, don't get evaluated until
they are called in the template. Therefore, if a quearyset call is
wrapped in an if statement in the template that evaluates to false,
the query should never happen. What are you trying to accomplish that
is any different?
Well, spam littered tickets would be worse. It's the lesser of two
evils. You can register [1] for an account and bypass the spam filter
-- Or, if you don't what to register, create a session [2] to get the
spam filter to go easy on you.
[1]: http://www.djangoproject.com/accounts/register/
[2]: http://code.djangoproject.com/settings
--
----
Waylan Limberg
way...@gmail.com
You probably should take a look at the ORM code.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
Once again, there's no high-level support, but qsrf added some
infrastructure which will make an eventual high-level implementation
easier, and which makes writing a manual implementation right now a
bit less tedious. Look at the constructor of
django.db.models.sql.query.Query for the "connection" argument.