And unless your application is extremely unusual, by far the biggest
expense is database queries. More than anything else, this is what
governs the speed of your application. So don't worry about where the
conditionals are being evaluated: worry about how much data you are
pulling from the da
On 3/12/07, Bill de hOra <[EMAIL PROTECTED]> wrote:
> Merric Mercer wrote:
>
> > 1. Design a template with lots of {% if %} conditional statements
> >
> > 2. Do the bulk of the work in the view, by doing something like:-
> >
> > 3. Do a combination of the two above
>
> 4: Caching?
5. Start
Merric Mercer wrote:
> 1. Design a template with lots of {% if %} conditional statements
>
> 2. Do the bulk of the work in the view, by doing something like:-
>
> 3. Do a combination of the two above
4: Caching?
cheers
Bill
--~--~-~--~~~---~--~~
You re
Merric Mercer wrote:
> I have view that returns a whole bunch of different variables and
> boolean flags.The state of these flags determine what the user
> actually sees on their screen.
>
> From a design perspective I seem to have two options:-
>
>
> 1. Design a template with lots of
I have view that returns a whole bunch of different variables and
boolean flags.The state of these flags determine what the user
actually sees on their screen.
From a design perspective I seem to have two options:-
1. Design a template with lots of {% if %} conditional statements to
5 matches
Mail list logo
