Fix some problems with schema name used to access information_schema

There will typically be _test & _development in the same volume. So need to specify which is needed.

This assumes that when the optional schema argument to various overloaded methods is not specified, it means the current schema of the connection, not a wildcard. That seems to make more things work.