On Dec 27, 8:21 pm, Don Arbow <[EMAIL PROTECTED]> wrote:
On Dec 27, 2006, at 5:44 PM, Jason C. Leach wrote:
> Specifically, I'm curious how you do it without putting SQL in the
> view. From what I understand about the methodology of MVC this should
> not be done.I would only worry about that
On 12/27/06, Don Arbow <[EMAIL PROTECTED]> wrote:
On Dec 27, 2006, at 5:44 PM, Jason C. Leach wrote:
> Specifically, I'm curious how you do it without putting SQL in the
> view. From what I understand about the methodology of MVC this should
> not be done.
I would only worry about that if
On Dec 27, 2006, at 5:44 PM, Jason C. Leach wrote:
Specifically, I'm curious how you do it without putting SQL in the
view. From what I understand about the methodology of MVC this should
not be done.
I would only worry about that if you are concerned about
maintainability or want to avoid
gt; wrote:
> > What do we do in Django if we want to use complex data models like
> > JOINs, or a shopping card with invoices and line-items? Do we try and
> > keep as much in the database as possible using stored procedures or
> > views?
> >
> > What happens to the
On 12/27/06, Jason C. Leach <[EMAIL PROTECTED]> wrote:
Hi:
Specifically, I'm curious how you do it without putting SQL in the
view. From what I understand about the methodology of MVC this should
not be done.
Jason, I'd encourage you to read the first tutorial, then fiddle with
the
in Django if we want to use complex data models like
> JOINs, or a shopping card with invoices and line-items? Do we try and
> keep as much in the database as possible using stored procedures or
> views?
>
> What happens to the model when you want to do more than just SELECT x,
>
On 12/27/06, Jason <[EMAIL PROTECTED]> wrote:
What do we do in Django if we want to use complex data models like
JOINs, or a shopping card with invoices and line-items? Do we try and
keep as much in the database as possible using stored procedures or
views?
What happens to the model wh
What do we do in Django if we want to use complex data models like
JOINs, or a shopping card with invoices and line-items? Do we try and
keep as much in the database as possible using stored procedures or
views?
What happens to the model when you want to do more than just SELECT x,
y, z FROM
8 matches
Mail list logo