Support multiple database connections in the SQLAlchemy storage implementation
Bug #1074093 reported by
Kiall Mac Innes
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Medium
|
Kiall Mac Innes |
Bug Description
Support multiple database connections in the SQLAlchemy storage implementation, this will allow for connections to additional databases e.g. PowerDNS.
The current use of global _ENGINE and _MAKER variables in session.py prevents this.
At the same time - we should continue to support multiple sessions on a single engine.
Changed in moniker: | |
milestone: | none → grizzly-1 |
assignee: | nobody → Endre Karlson (endre-karlson) |
importance: | Undecided → Wishlist |
status: | New → In Progress |
milestone: | grizzly-1 → none |
assignee: | Endre Karlson (endre-karlson) → nobody |
importance: | Wishlist → Undecided |
status: | In Progress → New |
Changed in moniker: | |
milestone: | none → grizzly-2 |
Changed in moniker: | |
assignee: | nobody → JC Martin (jemartin) |
importance: | Undecided → Medium |
Changed in moniker: | |
milestone: | grizzly-2 → grizzly-1 |
Changed in moniker: | |
assignee: | JC Martin (jemartin) → Kiall Mac Innes (kiall) |
Changed in designate: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Since Moniker and the backend might use different engines, it seems that the goal is more to provide a generic SQLAlchemy library to facilitate backend development.
This would allow each implementation to have its own engine, and each engine have multiple sessions.
In addition, the configuration related to SQLAlchemy should provide a kind of name space to allow the configuration of each engine independently