Hi, Moshe, thanks a lot for bringing this up. I remember I tried to find a way to change isolation level per connection but also was unable to do that. An advice from oslo team would be very helpful. Renat Akhmerov @ Mirantis Inc. > On 08 Dec 2015, at 13:41, ELISHA, Moshe (Moshe) <moshe.elisha at alcatel-lucent.com> wrote: > > Hi, > > We at Mistral want to move from the default transaction isolation level of REPEATABLE READ to READ COMMITTED as part of a bugfix[1]. > > I did not find a way to pass the isolation level to sqlachemy using oslo.db and the current solution is to use monkey-patching[2] that adds the “isolation_level” property. > > Is there currently a better way to set the default isolation level? > If not – I will create a BP for it. > > Thanks. > > [1] https://review.openstack.org/#/c/253819 <https://review.openstack.org/#/c/253819> > [2] https://review.openstack.org/#/c/253819/11/mistral/db/sqlalchemy/base.py <https://review.openstack.org/#/c/253819/11/mistral/db/sqlalchemy/base.py> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org <mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151208/913ecf0c/attachment.html>