For legacy reasons, the Neutron test suite creates and destroys a db for each
test. There is a patch proposed to create the tables once and then ensure the
tables are wiped at the end of each test [1], providing a performance
improvement of ~10%. I was wondering if this is the best way to
Nested commits in sqlalchemy should be seen as a single transaction on the
backend, shouldn't they?
I don't know anything about this specific problem, but the fact that unit
tests use sqlite might be a reason, since it's not really a full DBMS...
I think that wrapping tests in transaction also
I’ve done a lot of work on this issue and from my perspective, the code is
mostly ready to go, however we’re in an extended phase of getting folks to sign
off as well as that I’m waiting for some last-minute fixup from Robert Collins.
Patch: [1] Blueprint, which is to be moved to Kilo: [2]
