Opened 19 years ago
Closed 16 years ago
#1764 closed defect (worksforme)
OneToOneField doesn't validate if it's set
| Reported by: | Rudolph Froger | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| 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: | no | UI/UX: | no |
Description
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.
See:
http://groups.google.com/group/django-developers/browse_thread/thread/c1ec4105f3f4fa10
Change History (5)
comment:1 by , 18 years ago
| milestone: | Version 0.92 → Version 1.0 |
|---|
comment:3 by , 18 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
the model inheritance stuff is going to change this.
comment:4 by , 17 years ago
| Keywords: | 121-rewrite added |
|---|
comment:5 by , 16 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Looks like if it works now.
Note:
See TracTickets
for help on using tickets.
0.92 is long gone.