The recipe didn't work; it collects all tables, but no foreign keys and in the end removes nothing.
I am using this in tearDown of unit tests. I have the DB in memory and even create a new engine in setUp ... maybe I am overlooking somthing dumb, but I don't get it. I'll try using a sqlite file and closing and deleting the file in tearDown. Cheers, Lars On Feb 24, 2:28 pm, lars van gemerden <l...@rational-it.com> wrote: > Thanks very much, > > Nothing is ever easy ... :-( > > why not .. :-) > > On Feb 24, 2:11 pm, Chris Withers <ch...@simplistix.co.uk> wrote: > > > > > > > > > On 24/02/2012 12:40, lars van gemerden wrote: > > > > can it be possible that drop_all does not empty the database of there > > > are circular references between tables? > > > You want: > > >http://www.sqlalchemy.org/trac/wiki/UsageRecipes/DropEverything > > > ...which is available here too: > > >http://packages.python.org/mortar_rdb/api.html#mortar_rdb.drop_tables > > > cheers, > > > Chris > > > PS: > > > > I am using sqlite. > > > Why? ;-) > > > -- > > Simplistix - Content Management, Batch Processing & Python Consulting > > -http://www.simplistix.co.uk -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
