Concrete quantum database
Registered by
Trey Morris
Issues with current Quantum DB implementation:
Plugin schemas and core schema share same SA Base object
Plugins can't version DB separate from core schema
Each plugin can change the core schema if they use it
Plugins may not even use or populate the base quantum schema
Certain failures don't rollback correctly, leading to bad data
Plugin schemas are incompatible
Proposal:
all plugins should use a common engine
each plugin should maintain a separate db base object
Having a concrete core database in quantum gives us the ability to reliably use it outside the plugin. Not sure how to solve plugin not populating the db.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Mark McClain
Related branches
Related bugs
Sprints
Whiteboard
This ultimate goal of this work is likely to be covered by other db work. Closing this blueprint to avoid confusion.
(?)