| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The keystone.common.sql.core.Base class cached the global database
engine when get_session() was called. When the global database engine
changed to a new instance, the cached copy was used in subsequent
calls to get_session(), leading to using the old engine and tests
failing to run by themselves.
This change makes it so that when the global database engine is
changed, Base will use the new engine rather than the invalid one.
Change-Id: I75aa3c230d9b4fd666ab8d478c9e9a27669905e8
Fixes: Bug #1179259
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This change makes it so that the arguments for the session
creation function get_session() get passed on when it calls the
function to create the session.
Change-Id: I2f889ab36bd3aa3bf4441a13eb2b610b54349cbb
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
This adds functionality where a class can monitor for the global
engine changing.
This is useful for a class that caches the global engine and
wants to know when its cached global engine isn't valid anymore.
Part of fix for bug 1179259
Change-Id: I5736a05308c63de9fccb8af7720ddd70530f4270
|
|
|
This change makes it so that get_engine() in
keystone.common.sql.core.Base does not return the global engine
when allow_global_engine is False.
The behavior before could be described like:
If get_engine() has never been called with allow_global_engine=True,
then if you pass allow_global_engine=False returns a new engine.
Otherwise, you always get the global engine (even if
allow_global_engine=False)
The new behavior is:
If get_engine() is called with allow_global_engine=True then
it returns the global engine, otherwise it returns a new engine.
Change-Id: I756b54d9f3984733f56d09c11b2702c3451102f2
|
