You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?)
What would you like help with?
Is the intent of the
FOREIGN KEY
constraints returned byAdbcConnectionGetObjects
that they include relational constraints in both directions? That is, for aCUSTOMER
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.
The text was updated successfully, but these errors were encountered: