Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification on GetObjects FOREIGN KEY #2294

Open
CurtHagenlocher opened this issue Oct 30, 2024 · 1 comment
Open

Clarification on GetObjects FOREIGN KEY #2294

CurtHagenlocher opened this issue Oct 30, 2024 · 1 comment
Labels
Type: question Usage question

Comments

@CurtHagenlocher
Copy link
Contributor

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, 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.

@CurtHagenlocher CurtHagenlocher added the Type: question Usage question label Oct 30, 2024
@lidavidm
Copy link
Member

lidavidm commented Nov 6, 2024

I think from reading the GetObjects schema definition, only JDBC's getImportedKeys is supported, effectively. We would need to add something to cover getExportedKeys, probably by extending the constraint_type (adding EXPORTED KEY?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: question Usage question
Projects
None yet
Development

No branches or pull requests

2 participants