#2922: [patch] defining outer joins
----------------------------+-----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: reopened | Component: Database wrapper
Version: | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 1
Needs_tests: 1 | Needs_better_patch: 1
----------------------------+-----------------------------------------------
Comment (by Michael Radziej <[EMAIL PROTECTED]>):
Replying to [comment:5 mtredinnick]:
I'm finding, the more I use Django's ORM, that a way to turn an arbitrary
sql select command into a !QuerySet (provided it contains all the fields
of a model) would be the best idea to solve all the non-standard queries.
ORMs that try to solve everything seem to get more complicated than
writing custom sql ... But we should discuss this on the list. Would you
like to fan out your ideas on this refactoring there?
--
Ticket URL: <http://code.djangoproject.com/ticket/2922#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
