Opened 3 years ago

Closed 3 years ago

#19089 closed Bug (duplicate)

Incorrect reverse one-to-one lookup on unsaved objects

Reported by: aaugustin Owned by: nobody
Component: Database layer (models, ORM) Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Let's assume two models, A and B. A has a nullable one-to-one relation to B.

Let's create a single instance of A in the database, with no related B (a.b_id = None).

Now let's instanciate a B without saving it ( = None).

At this point, b.a incorrectly returns the instance of a created above -- because it's the only A with a.b_id == b.a should raise A.DoesNotExist instead.

Attachments (1)

19089.patch (2.0 KB) - added by aaugustin 3 years ago.

Download all attachments as: .zip

Change History (2)

Changed 3 years ago by aaugustin

comment:1 Changed 3 years ago by aaugustin

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

This is duplicate of #18153 (thanks Ramiro).

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