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 if you are concerned about
maintainability or want to avoid duplicating a query in more than one
view. In that case you could just create a Python file containing SQL
queries and import them where you need them.
MY_BIG_QUERY = """SELECT * FROM table WHERE ..."""
MY_BIG_QUERY_2 = """SELECT * FROM table2 INNER JOIN table3 WHERE ..."""
Don
Wouldn't it be better to include queries like this in a model's custom
manager as described in
http://www.djangoproject.com/documentation/model_api/#custom-managers?
I've done this a lot in my models. It keeps model logic encapsulated
in the model, and makes the API cleaner.
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
