format: granularity for constraints in AdbcConnectionGetObjects

[CurtHagenlocher]

Fetching constraints can be quite expensive if they're not going to be needed. AdbcConnectionGetObjects doesn't make it possible to get tables or columns without also fetching constraints. There should be a way to do so.

[lidavidm]

I'm also willing to consider breaking up getObjects to be less monolithic

[CurtHagenlocher]

I wonder whether we need an overall tracking item for metadata-related APIs. For now, I'm going to add an unrelated complaint to this one. The spec for GetObjects says

Some functions accept "search pattern" arguments, which are strings that can contain the special character "%" to match zero or more characters, or "_" to match exactly one character. (See the documentation of DatabaseMetaData in JDBC or "Pattern Value Arguments" in the ODBC documentation.) Escaping is not currently supported.

The lack of support for escaping means that fetching metadata for a table in a schema named release_test can be significantly slower than fetching metadata for a table in a schema named releasetest.

[lidavidm]

Ah, I think what we're missing is the equivalent of https://docs.oracle.com/en/java/javase/11/docs/api/java.sql/java/sql/DatabaseMetaData.html#getSearchStringEscape()

There are other issues asking about having the driver escape things; it might be good to provide those + provide a way to escape the search pattern per-driver (since it appears this is not commonly standardized unlike the pattern characters)