Schema management server-client communication failures on create, drop and catalog reads.

[carlsonjosh]

Create schema fails on client
I am getting an unclear error when creating a remote schema...

from a client:

install quack from core_nightly;
load quack;
attach 'quack:localhost' as remote (token 'asdf');
create schema if not exists remote.transform;

Returns: Catalog "remote" does not exist!. I think this should either explicitly fail or create the schema.

Drop schema fails on client

1. From an already running server... Running create schema drop_me; successfully creates a schema. 👍
2. Running show schemas on a new client shows remote | drop_me as a valid schema. 👍
3. From the client, running drop schema remote.drop_me fails with:

Not implemented Error:
DropSchema not implemented yet

It would be nice to have this implemented

Show schemas has old information
Back to the server from above... I can run drop schema drop_me from the server and it successfully deletes the schema. 👍
But running show schemas; on the same client still shows that as a valid catalog schema. 👎

Incidentally, the same happens with tables. I would expect the client to have a regular remote catalog refresh.

[pinei]

It seems the remote attachment works correctly if you explicitly switch to the remote catalog using USE before running the command

use remote;
create schema if not exists transform;