Nothing has changed regarding that recipe and I just ran it on a small set of tables against Postgresql (which I can see is the DB you're using) and it runs fine. Are you sure the identical schema *does* drop completely when this recipe is run directly with 0.7.8 ? Can you provide the structure of the schema which can't be dropped ?
On Dec 14, 2012, at 9:17 PM, Russ wrote: > I have just updated SQLAlchemy from 0.7.8 to 0.8.0b2 (the current pip > default) and the DropEverything recipe has stopped working. The problem is > on the DropTable line with this error : > > sqlalchemy.exc.InternalError: (InternalError) cannot drop table > test_list_name because other objects depend on it > > I'm currently trying to figure out how to fix it with the hint it gives > ("HINT: Use DROP ... CASCADE to drop the dependent objects too."), but at > the moment it is not clear to me how to do this. I'm out of my depth when it > comes to schema definition language changes. > > Does anyone know a quick fix? > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/sqlalchemy/-/okypK5IgUaoJ. > 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. -- 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.