-
-
Notifications
You must be signed in to change notification settings - Fork 233
Few problems with domains's check constraints [CORE1395] #1813
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
Comments
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 Beta 2 [ 10190 ] |
Modified by: @pcisarWorkflow: jira [ 12741 ] => Firebird [ 14437 ] |
Commented by: @pmakowski Q/A test ok |
Modified by: @pmakowskistatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Submitted by: Alexander Tyutik (tut)
Is related to QA179
Here is a script for making all necessary objects:
CREATE TABLE TEST ( ID INTEGER );
CREATE DOMAIN TEST_DOMAIN AS INTEGER CHECK (EXISTS(SELECT * FROM TEST WHERE ID=VALUE));
Now there are 3 problems:
1) Server didn't create any dependency
2) I can drop table TEST without any problems (think because of 1): DROP TABLE TEST;
3) After table was dropped i can make backup and restore without any problems. I think server should show some message at the end of beckup or restore log...
Commits: a568843
The text was updated successfully, but these errors were encountered: