I've only recently started working with SQLAlchemy, so I could be just having noob problems, but...
I've run into a problem while writing unit tests for my SQLAlchemy model. I have setUp and tearDown methods which create and drop my tables so that each test is run with a clean setup. All of the tables are being created, as shown by the generated SQL. What I discovered is that meta.drop_all() was failing to drop some of my tables. Not all, just some. It wasn't even generating the SQL to drop those tables. Changing the drop_all to a series of table.drop(checkfirst=True) calls showed the same symptom. When I removed the 'checkfirst=True' parameter from the drop calls, the problem went away, the SQL 'DROP' commands were generated for all the table.drop method calls, and all my tables were dropped. I am using SQLite as my backend, if this has any relevance to the problem. Is this a known issue, caused by a noob mistake, or is it something I need to put a ticket in on? ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
