Why are you testing with sqlite?

Chris

On 24/02/2012 14:32, lars van gemerden wrote:
OK, the file isn't closed ofcourse and i can't figure out how to close
it. I'll try some more and if nothing works probably start a new
post ...

Thanks anyway, Chris

On Feb 24, 3:02 pm, lars van gemerden<[email protected]>  wrote:
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<[email protected]>  wrote:







Thanks very much,

Nothing is ever easy ... :-(

why not .. :-)

On Feb 24, 2:11 pm, Chris Withers<[email protected]>  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


--
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 [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.

Reply via email to