Uniqueness constraint based on column value in a related table












0














I have 2 tables, let's call it users and groups. Some groups are by design singletons and must have exactly one user, and some groups can have multiple users.



users (
id
)

groups (
id
name
singleton
)

users_groups (
user_id
group_id
)


Is there a way to enforce the uniqueness constraint that would




  • disallow adding more than one user to singleton groups

  • remove singleton groups when its only user is deleted










share|improve this question


















  • 1




    Handling both these requirements is probably best accomplished with triggers.
    – Gordon Linoff
    Nov 21 at 3:09
















0














I have 2 tables, let's call it users and groups. Some groups are by design singletons and must have exactly one user, and some groups can have multiple users.



users (
id
)

groups (
id
name
singleton
)

users_groups (
user_id
group_id
)


Is there a way to enforce the uniqueness constraint that would




  • disallow adding more than one user to singleton groups

  • remove singleton groups when its only user is deleted










share|improve this question


















  • 1




    Handling both these requirements is probably best accomplished with triggers.
    – Gordon Linoff
    Nov 21 at 3:09














0












0








0







I have 2 tables, let's call it users and groups. Some groups are by design singletons and must have exactly one user, and some groups can have multiple users.



users (
id
)

groups (
id
name
singleton
)

users_groups (
user_id
group_id
)


Is there a way to enforce the uniqueness constraint that would




  • disallow adding more than one user to singleton groups

  • remove singleton groups when its only user is deleted










share|improve this question













I have 2 tables, let's call it users and groups. Some groups are by design singletons and must have exactly one user, and some groups can have multiple users.



users (
id
)

groups (
id
name
singleton
)

users_groups (
user_id
group_id
)


Is there a way to enforce the uniqueness constraint that would




  • disallow adding more than one user to singleton groups

  • remove singleton groups when its only user is deleted







mysql sql






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 at 2:05









vasily

1,6011326




1,6011326








  • 1




    Handling both these requirements is probably best accomplished with triggers.
    – Gordon Linoff
    Nov 21 at 3:09














  • 1




    Handling both these requirements is probably best accomplished with triggers.
    – Gordon Linoff
    Nov 21 at 3:09








1




1




Handling both these requirements is probably best accomplished with triggers.
– Gordon Linoff
Nov 21 at 3:09




Handling both these requirements is probably best accomplished with triggers.
– Gordon Linoff
Nov 21 at 3:09












1 Answer
1






active

oldest

votes


















0














Using triggers we can achieve these conditions.



There is another option , that would be to implement the functionality for "insert" and "delete" operations into stored procedures which would also check and remove singleton groups when its only user is deleted and also prevent addition of more than one user to the singleton groups






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2fstackoverflow.com%2fquestions%2f53404344%2funiqueness-constraint-based-on-column-value-in-a-related-table%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














    Using triggers we can achieve these conditions.



    There is another option , that would be to implement the functionality for "insert" and "delete" operations into stored procedures which would also check and remove singleton groups when its only user is deleted and also prevent addition of more than one user to the singleton groups






    share|improve this answer


























      0














      Using triggers we can achieve these conditions.



      There is another option , that would be to implement the functionality for "insert" and "delete" operations into stored procedures which would also check and remove singleton groups when its only user is deleted and also prevent addition of more than one user to the singleton groups






      share|improve this answer
























        0












        0








        0






        Using triggers we can achieve these conditions.



        There is another option , that would be to implement the functionality for "insert" and "delete" operations into stored procedures which would also check and remove singleton groups when its only user is deleted and also prevent addition of more than one user to the singleton groups






        share|improve this answer












        Using triggers we can achieve these conditions.



        There is another option , that would be to implement the functionality for "insert" and "delete" operations into stored procedures which would also check and remove singleton groups when its only user is deleted and also prevent addition of more than one user to the singleton groups







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 at 4:42









        George Joseph

        1,30249




        1,30249






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2fstackoverflow.com%2fquestions%2f53404344%2funiqueness-constraint-based-on-column-value-in-a-related-table%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

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            Refactoring coordinates for Minecraft Pi buildings written in Python