Opened 7 years ago

Closed 7 years ago

#7618 closed (invalid)

Multiple ForeignKeys to the same model produces wrong SQL statements (the same as in trunk)

Reported by: anonymous Owned by: nobody
Component: GIS Version: gis
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

After qs-refactoring GeoDjango has the same bug as trunk, ticket:7125. Ticket was fixed in changeset:7778, but in the GeoDjango branch bug still exist.

Change History (1)

comment:1 Changed 7 years ago by jbronn

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

Closing as invalid because I'm waiting to merge due to the changes made to WhereNode in r7773. Specifically, Malcolm & I have already discussed in private correspondence a change that will re-enable passing the Field instance into WhereNode.add (GeometryFields have metadata in their instance that need to be passed into WhereNode for spatial SQL construction).

In general, bugs shouldn't be reported for this branch unless they still exist after the changeset has been merged.

Note: See TracTickets for help on using tickets.
Back to Top