Describe the bug, including details regarding any error messages, version, and platform.
The flight-sql-jdbc-driver permits to set the catalog at connection time but silently ignores Connection.setCatalog() while being connected.
As a result, database browsers and other clients relying on setCatalog() will show various client-side errors, such as displaying the same set of tables regardless of what catalog you select, screwing up SQL code generation and so forth. (My test vehicle is DBVisualizer.)
To fix this issue, I propose to implement setCatalog() in the same way as already implemented during connection setup. I would set up a PR for this that demonstrates the issue using a failing test case in the first commit and a fix in the second commit.
Describe the bug, including details regarding any error messages, version, and platform.
The flight-sql-jdbc-driver permits to set the catalog at connection time but silently ignores Connection.setCatalog() while being connected.
As a result, database browsers and other clients relying on setCatalog() will show various client-side errors, such as displaying the same set of tables regardless of what catalog you select, screwing up SQL code generation and so forth. (My test vehicle is DBVisualizer.)
To fix this issue, I propose to implement setCatalog() in the same way as already implemented during connection setup. I would set up a PR for this that demonstrates the issue using a failing test case in the first commit and a fix in the second commit.