iain duncan wrote: > Thanks Mike. I figured this is probably not the intended use. The > thing is, I'm trying to make a declarative template for test seed data > and declaring it all in a class like so makes for the easiest quickest > way of extending my fixture: > > class SeedData1(SeedData): > obj1 = ModelObject( ...kwargs... ) > obj2 = ModelObject2( ...kwargs... > > This allows me to make new seed data fixtures by simply inheriting > from SeedData1, and makes typing up seed fixtures dead quick.
I don't see what this has to do with clearing out sessions and the objects that are associated within. Is SeedData1 some kind of magic class that persists obj1, obj2, etc. in the Session? why can't whatever SeedData1 does be done for each test ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
