Comment 3 for bug 1548960

okey doke, so I have something coming along that so far I'm testing a lot towards Neutron, since they have fixture use that hugs closely to what's in oslo.db. I'm developing the APIs here against oslo.db and implementing how neutron can use it at the same time, as a means of optimizing how the API is organized. So now we come to Nova, and I can see Nova has a nice simple system now, which is great, in the form of the nova.tests.fixtures.Database fixture. So I'm probably going to have to get discussion going on the ML about this, but for now I'm assuming the goal is, get Database to also work against mysql, Postgresql, etc., include systems for building up the database schema, and then do the right thing when we plug in MySQLOpportunisticTestCase and PsqlOpportunisticTestCase, right? Because the clever trick that Database is using right now with sqlite_connection.iterdump() isn't going to work w/ the other DBs. oslo.db's fixture has a whole way of doing all this using testresources but safe to assume I can propose changes to Database? Or is there something already in the works and you really really just need the one enginefacade method "enginefacade.please_connect_to_this_other_db_instead()" ? (the patch has that also).