A typo fix that fortunately wasn't creating invalid SQL, just slightly less
efficient than possible SQL in some odd cases (found via code inspection, not any particular failing example). git-svn-id: http://code.djangoproject.com/svn/django/trunk@8831 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
c7a10b677d
commit
3cdfb47e93
|
@ -738,7 +738,7 @@ class Query(object):
|
||||||
Returns True if the join was promoted.
|
Returns True if the join was promoted.
|
||||||
"""
|
"""
|
||||||
if ((unconditional or self.alias_map[alias][NULLABLE]) and
|
if ((unconditional or self.alias_map[alias][NULLABLE]) and
|
||||||
self.alias_map[alias] != self.LOUTER):
|
self.alias_map[alias][JOIN_TYPE] != self.LOUTER):
|
||||||
data = list(self.alias_map[alias])
|
data = list(self.alias_map[alias])
|
||||||
data[JOIN_TYPE] = self.LOUTER
|
data[JOIN_TYPE] = self.LOUTER
|
||||||
self.alias_map[alias] = tuple(data)
|
self.alias_map[alias] = tuple(data)
|
||||||
|
|
Loading…
Reference in New Issue