Enhancment - Allow Drop Database Script To Be Specified

[GoogleCodeExporter]

RoundhousE provides several options for customizing the process of creating a 
database. You can specify a particular script, and there is a folder for 
scripts to be run immediately after creation. This is very useful, especially 
if you need to redeploy the database, which happens fairly often during 
development.

However, for some databases, RoundhousE is unable to drop the "database". This 
makes sense, actually. Different database technologies have different concepts 
of what constitutes a database. In SQL server, one usually considers the 
"database" to be the physical file and all data associated with the file. 
Things like users are external, and schema can be used to logically organize 
the database. Oracle, on the other hand, associates users with a particular 
database and treats each user also as a schema. This has the effect of the 
conceptual "database" usually being thought of as an individual schema. In the 
technologies I've worked with, it is a relatively simple process to script the 
drop, but the drop must be performed by another tool since users can't override 
how RoundhousE performs the drop. This forces RoundhousE users to build up a 
significant amount of infrastructure to automate redeployment and to depend on 
extra tools that otherwise would not be needed.

Original issue reported on code.google.com by [email protected] on 3 Dec 2011 at 11:37