"Constraint not satisfied" should be reworded and trigger a logged error
Bug #28655 reported by
Matthew Paul Thomas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
"Constraint not satisfied" means nothing unless you know a lot about databases, and even if you do, it doesn't tell you what's wrong with the field.
Therefore:
(1) It should be reworded to "This field is incorrect."
(2) Whenever the error happens, it should be logged in Launchpad's error reports the same way oopses and timeouts are, so making the error message useful can be treated with similar seriousness.
| Changed in launchpad: | |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Karl Fogel (kfogel) wrote | #1 |
| affects: | launchpad-foundations → launchpad-web |
To post a comment you must log in.
If this is fixed, a number of bugs that currently are described in terms of the "constraint not satisfied" error (such as bug #95193 and bug #297833) should probably have their summaries and/or descriptions edited to reflect whatever the new error in each case is.
https:/