krlmlr commented on PR #18: URL: https://github.com/apache/arrow-adbc/pull/18#issuecomment-1159732527
I wonder if we also should offer a way to expose primary and foreign key, and perhaps unique constraints. This allows learning the data model from a remote database. I have devised a "minimum variant" of a sane `INFORMATION_SCHEMA` that allows storing this information. Of course no database (except perhaps DuckDB) implements this schema, tweaks are needed everywhere else. Essentially this consists of three new views, linked 1:n: `tables` <- `table_constraints` <- `key_column_usage` <-`constraint_column_usage` . This would only require an extra column in our "tables" element, implementers could leave it empty. What do you think? I'd be excited to see it here, happy to provide guidance if we agree to move forward. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
