> Look at the constructor of django.db.models.sql.query.Query for the
> "connection" argument.
You know, I grepped on that but didn't see anything interesting. Now
with a two-beer-handicap, I'll go with Blanche DuBois -- Tomorrow is
another day.
On Fri, May 9, 2008 at 9:27 PM, Peter Rowell <[EMAIL PROTECTED]> wrote:
> OK, I'll bite. I kind of doubt he rewrote the templating system in the
> ORM, so you must be inferring that multiple database support was part
> of the qs-refactoring. I just checked out trunk and I'll admit I'm
> working
> You probably should take a look at the ORM code.
OK, I'll bite. I kind of doubt he rewrote the templating system in the
ORM, so you must be inferring that multiple database support was part
of the qs-refactoring. I just checked out trunk and I'll admit I'm
working with a one-beer-handicap at
On Fri, May 9, 2008 at 9:01 PM, Peter Rowell <[EMAIL PROTECTED]> wrote:
> Now that Malcolm has subclassable models working, my number one
> complaint is the templating system. Number two is single DB, but I can
> work around that more easily.
You probably should take a look at the ORM code.
--
> QuerySets are lazy [...] What are you trying to accomplish that is any
> different?
I'm working around the fact that Django's templates can't take
arguments. So I'm calling formatting functions which *do* take
arguments, one of which is a QuerySet. Of course, I can't pass args to
a function
On Fri, May 9, 2008 at 8:12 PM, Peter Rowell <[EMAIL PROTECTED]> wrote:
>
[snip]
> In order to delay a *very* expensive DB operation, I decided to put it
> in a function and pass the function as a context variable. The
> template uses fragment caching with vary_on, so only if the template
>
On Saturday 10 May 2008 03:23:39 Peter Rowell wrote:
> BTW, I tried to add a comment on this to
> http://code.djangoproject.com/ticket/7153, but got "Internal Server Error
> (Submission rejected as potential
> spam)", which struck me as rather rude. :-)
>
I was just gonna point you to #7153.
I
BTW, I tried to add a comment on this to
http://code.djangoproject.com/ticket/7153,
but got "Internal Server Error (Submission rejected as potential
spam)", which struck me as rather rude. :-)
--~--~-~--~~~---~--~~
You received this message because you are
Short version:
Callable context variables do not get called during resolution. If
invoked as a simple variable they return something like . If used in a for loop, they blow up the template. I'm
running trunk:7374
Longer version:
In order to delay a *very* expensive DB operation, I decided
