#6018: [patch] depth handling in fill_table_cache broken when using
select_related(depth=1).extra()
----------------------------------------------------+-----------------------
Reporter: Matthias Urlichs <[EMAIL PROTECTED]> | Owner: nobody
Status: new | Component: Database
wrapper
Version: SVN | Keywords:
Stage: Unreviewed | Has_patch: 1
----------------------------------------------------+-----------------------
As reported by [EMAIL PROTECTED] in #3275:
There is a bug in the way depth is handled in fill_table_cache, see ''the
attached patch'' for a test case. When you specify a non-zero depth
fill_table_cache goes one relationship too deep which causes
get_cached_row not to handle all the columns from select_related.
This bug shows up when you use extra on that Query``Set: the extra fields
to select should immediately follow columns handled by get_cached_row, but
instead they get data from the relationship that fill_table_cache added
and get_cached_row skipped.
----
I'm re-posting this bug (and his patches) here because #3275 is,
essentially, an unrelated ticket; IMHO this here patch should go into
mainline ASAP.
--
Ticket URL: <http://code.djangoproject.com/ticket/6018>
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
-~----------~----~----~----~------~----~------~--~---
