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
Bad error message when tring to create FK to non-existent table [CORE945] #1346
Comments
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 [ 10041 ] assignee: Adriano dos Santos Fernandes [ asfernandes ] |
Commented by: @pcisar Fix confirmed for 2.1 Alpha 1. Test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: @pcisar Reopened to update ticket information. |
Modified by: @pcisarWorkflow: jira [ 11230 ] => Firebird [ 15080 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Done successfully |
Submitted by: Ain Valtin (ain)
Is related to QA85
CREATE TABLE TAB_TestA (
UID INTEGER NOT NULL PRIMARY KEY
);
CREATE TABLE TAB_TestB (
UID INTEGER NOT NULL PRIMARY KEY,
TestA INTEGER CONSTRAINT FK_TestA REFERENCES TABTestA(UID) ON UPDATE CASCADE
);
Note that in the declaration on FK there is typo in table name - "TABTestA" instead of "TAB_TestA". This script raises very unhelpful error message:
---------------------------
Error
---------------------------
Error at line 5 - unsuccessful metadata update
could not find UNIQUE INDEX with specified columns
SQL - CREATE TABLE TAB_TestB (
UID INTEGER NOT NULL PRIMARY KEY,
TestA INTEGER CONSTRAINT FK_TestA REFERENCES TABTestA(UID) ON UPDATE CASCADE
)
---------------------------
Abort Ignore
---------------------------
Commits: f32795f 597cd78
The text was updated successfully, but these errors were encountered: