Bruno Dumon wrote:
> Perhaps move from a single Connection member on JdbcMeta to some factory
> that could getOrCreate Connections based on the caller's properties?
>
JdbcMeta already manages client-specific connections, the single connection
is marked for removal:
private final Connection connection; // TODO: remove default connection
private final Cache<String, Connection> connectionCache;
I did manage to add an OpenConnection rpc request that allows passing
properties, and it seems to work just fine, though the implementation does
make one strange jump. I'll looktomorrow to share it via jira.
Oh, well excuse me then. You totally did what I was thinking already.
Sorry for the confusion I made :)
