Unfavorable naming of feature "MySQL login enabled"

See title. I was thinking back and forth if this should be called a "bug" or rather a "task". :)

Thing is, the MySQL feature does not only comprise the login, but also all databases created for the vserver. So, when turning it off, not only the "MySQL login", but also all databases will get deleted.

Of course there is an appropriate warning that this is going to happen, still I think it would be clearer if the feature was called like "MySQL databases enabled?" and not just "login".