SQL - referential integrity - Foreign key and Check constraint












0















Please let me know if below two declarations are same.



create table R1
( a INT PRIMARY KEY,
b INT references K(w));


Note: K is a table with single attribute w as primary key



create table R1
( a INT PRIMARY KEY,
b INT CHECK (b in (SELECT w FROM K));









share|improve this question
















bumped to the homepage by Community 17 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • If K(w) is a primary or unique key, they are similar declarations. But most SQL products accept only the first syntax (FOREIGN KEY constraint) and not the second (which has a subquery in a CHECK constraint)

    – ypercubeᵀᴹ
    Jun 16 '14 at 8:52


















0















Please let me know if below two declarations are same.



create table R1
( a INT PRIMARY KEY,
b INT references K(w));


Note: K is a table with single attribute w as primary key



create table R1
( a INT PRIMARY KEY,
b INT CHECK (b in (SELECT w FROM K));









share|improve this question
















bumped to the homepage by Community 17 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • If K(w) is a primary or unique key, they are similar declarations. But most SQL products accept only the first syntax (FOREIGN KEY constraint) and not the second (which has a subquery in a CHECK constraint)

    – ypercubeᵀᴹ
    Jun 16 '14 at 8:52
















0












0








0








Please let me know if below two declarations are same.



create table R1
( a INT PRIMARY KEY,
b INT references K(w));


Note: K is a table with single attribute w as primary key



create table R1
( a INT PRIMARY KEY,
b INT CHECK (b in (SELECT w FROM K));









share|improve this question
















Please let me know if below two declarations are same.



create table R1
( a INT PRIMARY KEY,
b INT references K(w));


Note: K is a table with single attribute w as primary key



create table R1
( a INT PRIMARY KEY,
b INT CHECK (b in (SELECT w FROM K));






referential-integrity






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 16 '14 at 8:50









ypercubeᵀᴹ

75.5k11128211




75.5k11128211










asked Jun 16 '14 at 7:27









PhaniPhani

1




1





bumped to the homepage by Community 17 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 17 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • If K(w) is a primary or unique key, they are similar declarations. But most SQL products accept only the first syntax (FOREIGN KEY constraint) and not the second (which has a subquery in a CHECK constraint)

    – ypercubeᵀᴹ
    Jun 16 '14 at 8:52





















  • If K(w) is a primary or unique key, they are similar declarations. But most SQL products accept only the first syntax (FOREIGN KEY constraint) and not the second (which has a subquery in a CHECK constraint)

    – ypercubeᵀᴹ
    Jun 16 '14 at 8:52



















If K(w) is a primary or unique key, they are similar declarations. But most SQL products accept only the first syntax (FOREIGN KEY constraint) and not the second (which has a subquery in a CHECK constraint)

– ypercubeᵀᴹ
Jun 16 '14 at 8:52







If K(w) is a primary or unique key, they are similar declarations. But most SQL products accept only the first syntax (FOREIGN KEY constraint) and not the second (which has a subquery in a CHECK constraint)

– ypercubeᵀᴹ
Jun 16 '14 at 8:52












1 Answer
1






active

oldest

votes


















0














Not exactly - with your second CREATE statement, the same value of b can occur multiple times in table K, whereas with the first statement, it will occur once and once only. It's unusual - what are you trying to achieve?






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f68292%2fsql-referential-integrity-foreign-key-and-check-constraint%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Not exactly - with your second CREATE statement, the same value of b can occur multiple times in table K, whereas with the first statement, it will occur once and once only. It's unusual - what are you trying to achieve?






    share|improve this answer




























      0














      Not exactly - with your second CREATE statement, the same value of b can occur multiple times in table K, whereas with the first statement, it will occur once and once only. It's unusual - what are you trying to achieve?






      share|improve this answer


























        0












        0








        0







        Not exactly - with your second CREATE statement, the same value of b can occur multiple times in table K, whereas with the first statement, it will occur once and once only. It's unusual - what are you trying to achieve?






        share|improve this answer













        Not exactly - with your second CREATE statement, the same value of b can occur multiple times in table K, whereas with the first statement, it will occur once and once only. It's unusual - what are you trying to achieve?







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 16 '14 at 8:30









        VéraceVérace

        16k33350




        16k33350






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f68292%2fsql-referential-integrity-foreign-key-and-check-constraint%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            SQL Server 17 - Attemping to backup to remote NAS but Access is denied

            Always On Availability groups resolving state after failover - Remote harden of transaction...

            Restoring from pg_dump with foreign key constraints