Mercurial > kallithea
diff README.rst @ 6520:10f16cf8289e
cleanup: remove SQLAlchemy session argument to action_logger
There's always a global SQLAlchemy session associated with the current
thread; using another session for a single function call does not make
any sense (as sessions cannot be mixed), unless the code works carefully
to ensure the two sessions (and all objects loaded from them) are kept
completely separate. Suffice to say that Kallithea does no such thing,
thus there's no need to pretend to support multiple concurrent sessions.
author | Søren Løvborg <sorenl@unity3d.com> |
---|---|
date | Mon, 27 Feb 2017 19:47:54 +0100 |
parents | 0b6d2ca7175f |
children | d5eaa70e0f2a |