Opened 16 years ago
Last modified 13 years ago
#8209 closed
ModelForms (and hence the admin) don't check unique constraints — at Version 1
| Reported by: | glenjamin | Owned by: | nobody |
|---|---|---|---|
| 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.
Change History (1)
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 |
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 :)