CurtHagenlocher opened a new issue, #2294: URL: https://github.com/apache/arrow-adbc/issues/2294
### What would you like help with? Is the intent of the `FOREIGN KEY` constraints returned by `AdbcConnectionGetObjects` that they include relational constraints in both directions? That is, for a `CUSTOMER` table defined as in [TPC-H](https://docs.snowflake.com/en/user-guide/sample-data-tpch), should it return both `"ORDERS"."CUSTKEY"` (which references `"CUSTOMER"."CUSTKEY"`) and `"NATION"."NATIONKEY"` (which is referenced by `"CUSTOMER"."NATIONKEY"`)? If so, the documentation could probably be improved by indicating this explicitly. If not, if it only returns references in one direction then this is a feature gap with ODBC and JDBC. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
