when a PG database is hosed for me like that I log in and drop the key tables using "drop....cascade". Then a SQLA script can drop the rest assuming theres no more cycles.
On Jun 19, 3:16 pm, [EMAIL PROTECTED] wrote: > hi > i just run into a bad loop of > - creating some schema in postgres > - error in the middle of creation > - the schema is left in some sorry-state, half there half not > - next run, it complains about things (constraints etc) not present > as the tables are there but constraints not. > - dropall does not work complaining about 'cannot drop A as other > stuff depends on it' > only killing the whole db solved this mess. > any better way to deal with such things? > in this case i just wanted to start a new.. > i see postgres has some "drop..cascade" construct.. can that be used? > ciao > svil --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
