am back in the timesink of fighting with my db fixtures library. the stuff i want it to do is apparently just complicated enough that it doesn't work all the time.
i'd used a workaround for a bunch of stuff originally, and just discovered i didn't technically need to. so now i'm scaling back what i'm using the workaround for, and trying to decide if it's worth fighting the errors popping up along the way.
i'd be gaining test readability, so i feel like it's worth _some_ time.
so the fixture teardown method was attempting to delete all the fixture data. only some of my tests had...already deleted the fixture data. and the teardown method gets unhappy when what it deletes doesn't match what it created.
for now this is all being applied to an in-memory sqlite db (yes, i know that leaves holes in my tests), so i'm just going to skip it for now. when i move off sqlite, i'll rewrite the offending tests so the fixtures can clean up after themselves.
