Use a Filter API with SQLAlchemy Engine Events for Error Wrapping
The system that oslo.db provides for transformation of SQLAlchemy execution-
time errors, including DBAPI and related errors, should be reworked
to be simpler, more portable, more forwards-
and more testable.
Blueprint information
- Status:
- Complete
- Approver:
- Doug Hellmann
- Priority:
- Undefined
- Drafter:
- Mike Bayer
- Direction:
- Needs approval
- Assignee:
- Mike Bayer
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- 1.0.0
- Started by
- Doug Hellmann
- Completed by
- Doug Hellmann
Related branches
Related bugs
Sprints
Whiteboard
Not sure which milestone I should use here.
Gerrit topic: https:/
Addressed by: https:/
Add use-events-
Addressed by: https:/
- implement exception compatibility layer - work up a system of filters to replace imperative exception handling logic with declarative logic - fully move all exception reraises to be rules
Here's the SQLAlchemy feature: http://
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
Addressed by: https:/
Implement new exception interception and filtering layer
Addressed by: https:/
Add disconnect modification support to exception handling
Addressed by: https:/
Integrate the ping listener into the filter system.
Addressed by: https:/
Port _is_db_
Gerrit topic: https:/