Opened 10 years ago

Closed 8 years ago

#1764 closed defect (worksforme)

OneToOneField doesn't validate if it's set

Reported by: Rudolph Owned by: nobody
Component: Core (Other) Version: master
Severity: major Keywords: 121-rewrite
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


When a user in the admin interface "forgets" to set the OneToOneField and saves the object, Django does not return a nice error message but throws an exception because Django tries to insert a record without the primary key set. Some kind of validation should be added to prevent this.

Change History (5)

comment:1 Changed 10 years ago by Gary Wilson <gary.wilson@…>

  • milestone changed from Version 0.92 to Version 1.0

0.92 is long gone.

comment:2 Changed 9 years ago by anonymous

  • milestone Version 1.0 deleted

Milestone Version 1.0 deleted

comment:3 Changed 9 years ago by Gary Wilson <gary.wilson@…>

  • Triage Stage changed from Unreviewed to Design decision needed

the model inheritance stuff is going to change this.

comment:4 Changed 8 years ago by jacob

  • Keywords 121-rewrite added

comment:5 Changed 8 years ago by kratorius

  • Resolution set to worksforme
  • Status changed from new to closed

Looks like if it works now.

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