BUG for dropping database,Unexpect operation for dropping non-current database

[FriedEggsWithLeek]

OrientDB Version: 3.0.11

Java Version: 1.8

OS: Centos6.9

Expected behavior

connected remote to a2
then
drop database a1

Actual behavior

drop database a2

Steps to reproduce

[luigidellaquila]

Hi @FriedEggsWithLeek

Sorry, it's just a misunderstanding on the usage of drop database and a missing check in the code.

drop database can be used in two ways:

drop database [<storageType>]

that drops current database, and where is a legacy parameter (it could be local or plocal, but it doesn't make any sense now), that is just ignored, or

drop database <dbUrl> <username> <password>

You are using the first option, but since the storage type is ignored, you are not having any feedback and your current DB is being dropped.

I just added a check, so that you enter an invalid storage type you won't have this unexpected drop anymore.

The fix is already on 3.0.x branch and will be released with v 3.0.12

Thanks

Luigi