#8209 closed (fixed)
ModelForms (and hence the admin) don't check unique constraints
| Reported by: | glenjamin | Owned by: | Alex Gaynor |
|---|---|---|---|
| Component: | Forms | Version: | dev |
| Severity: | Keywords: | 1.0-blocker | |
| Cc: | tomek+django@… | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
They don't - in fact in SQLite a raw exception is propagated all the way up.
Attachments (7)
Change History (19)
comment:1 by , 16 years ago
| Component: | Documentation → Forms |
|---|---|
| Description: | modified (diff) |
| milestone: | → 1.0 |
| Summary: | Admin documentation claims that uniqueness is enforced in the interface → ModelForms (and hence the admin) don't check unique constraints |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 16 years ago
| Cc: | added |
|---|
comment:3 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
by , 16 years ago
| Attachment: | 8209_model_forms_unique.diff added |
|---|
comment:5 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:6 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | assigned → new |
I've got a patch that I will upload shortly.
by , 16 years ago
| Attachment: | django-r8769-8209.diff added |
|---|
comment:7 by , 16 years ago
| Keywords: | 1.0-blocker added |
|---|
by , 16 years ago
| Attachment: | 8209_modelform_unique_validation.1.diff added |
|---|
added a patch for review
comment:9 by , 16 years ago
| Has patch: | set |
|---|
comment:11 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Actually, I think ModelForms need to learn how to understand the unique stuff. I'm hijaking this ticket for that :)