What’s the best way to prevent running dropAll in the wrong database.
Is there any precondition that could prevent running dropAll based on some condition (maybe a table name)?
What’s the best way to prevent running dropAll in the wrong database.
Is there any precondition that could prevent running dropAll based on some condition (maybe a table name)?
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Exists-preconditions, offline databases and generated SQL | 0 | 814 | May 6, 2015 | |
| dropAll and oracle queue tables | 0 | 607 | October 2, 2012 | |
| DB2 Alias dropAll, attempts to drop table instead of alias | 0 | 353 | February 25, 2013 | |
| custom sql irreversible on dropall | 1 | 475 | July 18, 2012 | |
| Problems with dropAll and Firebird | 2 | 468 | October 13, 2009 |