Opened 10 years ago
Closed 10 years ago
#22375 closed Cleanup/optimization (duplicate)
Suggest to validate unique before running clean in models full_clean etc..
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.5 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
If we use clean(), and check for fields the hasn't been assigned, then it will raise a doesnotexist exception.
The clean() method claims we can utilize fields which data is clean, it's not. While in validation of uniqueness, the missing of fields will be suggested successfully, I think we should check if the field exists first.
Note:
See TracTickets
for help on using tickets.
Duplicate of #22374.