On Tue, Nov 22, 2011 at 1:39 AM, dmitry b <[email protected]> wrote: > Hi Russ, > > Thanks for a quick response. > > I don't think Django needs to make the decision of whether or not to > do a join. That can be done by the underlying database as long as > Django generates a query that the database can understand and optimize > properly.
This assumes that databases are equally good at performing optimizations of this kind. It's true that PostgreSQL does, and I believe that Oracle does as well; however, MySQL and SQLite are not equally blessed (to the best of my knowledge). Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en.
