Explicitly provide a DB context when executing a DB transaction
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
New
|
Wishlist
|
Unassigned |
Bug Description
Currently, when Neutron executes DB transaction, if there is no active session (or session at all), ``neutron_
That's a safeguard for the code written in Neutron but an inefficient way to access to the DB. Reader context allows, for example, the ASYNC_READER mode:
"""
This state indicates that the transaction is a read-only and is
safe to use on an asynchronously updated slave database.
"""
That is supposed to be less blocking than a writer context.
When the ``neutron_
This bug is just a tracker for all the patches needed to decorate all the DB transactions.
[1]https:/
[2]https:/
Changed in neutron: | |
importance: | Undecided → Wishlist |
tags: | added: db |