You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Ian Maxon (Jira)" <ji...@apache.org> on 2023/12/01 18:10:00 UTC

[jira] [Updated] (ASTERIXDB-3317) Tabular view FOREIGN KEY clause is name-deficient

     [ https://issues.apache.org/jira/browse/ASTERIXDB-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ian Maxon updated ASTERIXDB-3317:
---------------------------------
    Labels: triaged  (was: )

> Tabular view FOREIGN KEY clause is name-deficient
> -------------------------------------------------
>
>                 Key: ASTERIXDB-3317
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3317
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: COMP - Compiler, SQL - Translator SQL++
>    Affects Versions: 0.9.9
>            Reporter: Michael J. Carey
>            Assignee: Peeyush Gupta
>            Priority: Major
>              Labels: triaged
>             Fix For: 0.9.9
>
>
> Right now the FOREIGN KEY clause for tabular views is badly deficient.
> Its REFERENCES target must just be the name of a targeted tabular view.
> Like SQL, this needs to be a targeted tabular view with a parenthetical field name list so that one's foreign fields can be differently named than the targeted primary key fields.
> For example:
> ... FOREIGN KEY (orderno, itemno) REFERENCES items_view NOT ENFORCED
> versus
> ... FOREIGN KEY (orderno, itemno) REFERENCES items_view (ono, ino) NOT ENFORCED
> The former requires name matching while the latter, like SQL, allows the names to be different.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)