#18350: Incorrect behavior when inadvertently building a query using two different models. -------------------------------------+------------------------------------- Reporter: django@… | Owner: nobody Type: Bug | Status: new Component: Database layer | Version: 1.4 (models, ORM) | Resolution: Severity: Normal | Triage Stage: Accepted Keywords: query model | Needs documentation: 0 incorrect behavior | Patch needs improvement: 0 Has patch: 0 | UI/UX: 0 Needs tests: 0 | Easy pickings: 0 | -------------------------------------+-------------------------------------
Comment (by anonymous): I just got bitten by this bug again (different project). Is there a fix possible? -- Ticket URL: <https://code.djangoproject.com/ticket/18350#comment:2> Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/079.a1f1b0074a80d3e95bf9422a5358fdbd%40djangoproject.com. For more options, visit https://groups.google.com/groups/opt_out.