Databases such as SQL Server and PostgreSQL have the concept of catalogs as containers of database schemas. Users can usually specify an initial catalog during the connection process, list catalogs, and sometimes change catalogs during the session.
Currently catalog support in Flight SQL is somewhat limited. The protocol provides a way to list catalogs as well as metadata in SqlTypeInfo for reporting how catalogs are supported from a syntax perspective. ODBC and JDBC provide API calls for changing the catalog. Additionally, Flight SQL doesn't really provide the concept of "initial" connection properties (such as a starting catalog) since Flight itself is stateless from a connection perspective. To support catalogs properly, I'd imagine we need to make some changes to the Flight SQL protocol: - Introduce the concept of connection-time properties (perhaps an optional RPC for Flight SQL applications that need this) - Related to the above, expand the connection URL and Java builder to allow arbitrary application-specific properties. - Add optional RPCs for changing the catalog and relevant error codes if this is not permitted. -- *James Duong* Lead Software Developer Bit Quill Technologies Inc. Direct: +1.604.562.6082 | jam...@bitquilltech.com https://www.bitquilltech.com This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.
