Presenting Database Errors
Registered by
Mark Shuttleworth
on 2005-11-07
Launchpad should handle database errors more gracefully. In many cases, database errors are caused by the correct enforcement of database contraints. Currently, that causes a server error (500) rather than giving the user reasonable feedback about what they tried to do.
For example, if you try to add a specification to a product with the same name as an existing specification, you will see a "server error". What is really happening is that the database constraint on name uniqueness is being violated, trigerring a database error and then a launchpad server error. Instead, the user should see a meaningful alert and have the opportunity to correct it.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Alexander
- Priority:
- Medium
- Drafter:
- Stuart Bishop
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Mark Shuttleworth on 2006-08-16
- Completed by
- Mark Shuttleworth on 2006-08-16
Whiteboard
(?)