Changes between Initial Version and Version 2 of Ticket #13934


Ignore:
Timestamp:
07/14/2010 03:01:07 PM (5 years ago)
Author:
jbronn
Comment:

Obviously, the code needs to be synced up. However, the existing tests for select_related aren't blowing up -- can you provide a simple example that raises the TypeError? I want to explicitly test for the condition that induces the failure to ensure it doesn't regress.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13934

    • Property Status changed from new to assigned
    • Property Patch needs improvement unset
    • Property Needs tests unset
    • Property Milestone changed from to 1.3
    • Property Owner changed from nobody to jbronn
    • Property Needs documentation unset
  • Ticket #13934 – Description

    initial v2  
    1 If you try to {{{select_related()}}} with a {{{GeoManager}}}, things get pretty nasty with Django 1.2.
     1If you try to `select_related()` with a `GeoManager`, things get pretty nasty with Django 1.2.
    22
    3 You get a {{{TypeError}}}, claiming that {{{get_default_columns()}}} does not support the {{{local_only}}} parameter.
     3You get a `TypeError`, claiming that `get_default_columns()` does not support the `local_only` parameter.
    44
    55Included is a patch that ports the functionality over.
Back to Top