SQL Storage Driver
If we use SQLAlchemy, then this storage back-end may be a replacement for sqlite's (TBD). If we don't use SQLAlchemy, then we will only support MySQL.
Blueprint information
- Status:
- Complete
- Approver:
- Flavio Percoco
- Priority:
- Essential
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Yeela Kaplan
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Flavio Percoco
- Completed by
- Kurt Griffiths
Related branches
Related bugs
Sprints
Whiteboard
With sqlalchemy core, should be fairly easy.
<flaper87>
We need to discuss whether we want to use sqlalchemy or not. There are some benefits:
* Simplicity
* Support for multiple dbs with a single implementation
* Migrations
There are also some cons related to performance and speacial tweaks for different implementations.
http://
P.S: This is required for graduation
</flaper87>
Gerrit topic: https:/
Addressed by: https:/
Implement DataDriver for sqlalchemy storage backend
Addressed by: https:/
Implement tables and unit tests for sqlalchemy storage backend
Addressed by: https:/
feat(
Addressed by: https:/
feat(
Addressed by: https:/
[WIP]Extend driver functionality for sqlalchemy storage backend
Addressed by: https:/
[WIP]Implement Queue controller for sqlalchemy storage backend
Addressed by: https:/
Sqlalchemy Message controller
Addressed by: https:/
feat(
Addressed by: https:/
[WIP]Implement Claim controller for sqlalchemy storage backend
Addressed by: https:/
Add an sqlalchemy storage to Marconi
Addressed by: https:/
Add an sqlalchemy storage to Marconi
Addressed by: https:/
Enable pragma foreing key for sqlite
Addressed by: https:/
Fix message's get and deletion
Addressed by: https:/
Register sqlalchemy endpoints
Addressed by: https:/
Don't raise `DoesNotExist` on claims deletion
Addressed by: https:/
Deprecate sqlite in favor of sqlalchemy
Gerrit topic: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.
