Drop Schema without drop Database

[Hannes-Schniz]

Is your feature request related to a problem? Please describe.
In enterprise environments it is usually not possible to entirely drop and recreate the database each time you want to remove/recreate the schema. Furthermore Databases usually undergo a tuning process which is not possible when using the database right after creation.

Describe the solution you'd like
Id like to have the drop schema function not simply drop the database. In Db2 and PostgreSQL I implemented this in Version 4.12

Describe alternatives you've considered
The only other way to delete the schema is doing this manually which is defeating the purpose of the function entirely

Additional context

[sm-shaw]

Hi many thanks for the issue. The intention of this feature by request was to have the HammerDB workload completely self-contained, so for all databases it can create a database but gives the option of using a pre-existing one and then once the workload is complete has the option to clean-up after itself.
But yes, if the database was already pre-existing then it is doing more for the delete as it is undoing the users work to remove the pre-existing database, so does seem reasonable.
One option here is to try and set a flag if the schema already existed for the last database build and if it did then the next schema delete step will not drop the database, just remove the schema. As it is the Virtual User that checks for schema existence and not main HammerDB instance, the best way to do this would be via a TSV (thread shared variable). This way additional parameters are not required and we just maintain a flag to change behaviour in the delete script with the current drop everything being the default.