How can I add an additional unique_together constraint to Django Guardian object level permissions?












0















Using the example from the docs, let's assume I have a Task model:



class Task(models.Model):
summary = models.CharField(max_length=32)
content = models.TextField()
reported_by = models.ForeignKey(User, on_delete=models.CASCADE)
created_at = models.DateTimeField(auto_now_add=True)

class Meta:
permissions = (
('view_task', 'View task'),
)


Let's say I have many users on my app, and I want to make sure of the following at the database level:




  • No user has a duplicate task, i.e., a user can only have one task called "Sweep the floor."

  • Users do not share tasks. For instance, if two users have a task "Sweep the floor.", there should be two tasks with the summary "Sweep the floor." on the backend, one for each of the two users

  • I cannot add a user field on the Task model - I have to assign ownership of Task objects via permissions


Out of the box, the django_guardian UserObjectPermission has this unique_together constraint:



unique_together = ['user', 'permission', 'object_pk']


I think what I am looking for is a unique_together constraint that is more like this pseudo-code:



unique_together = ['user', 'permission', 'object_pk', 'task__summary']


Or, is there another way to enforce this type of uniqueness at the database level using Django Guardian permissions?










share|improve this question



























    0















    Using the example from the docs, let's assume I have a Task model:



    class Task(models.Model):
    summary = models.CharField(max_length=32)
    content = models.TextField()
    reported_by = models.ForeignKey(User, on_delete=models.CASCADE)
    created_at = models.DateTimeField(auto_now_add=True)

    class Meta:
    permissions = (
    ('view_task', 'View task'),
    )


    Let's say I have many users on my app, and I want to make sure of the following at the database level:




    • No user has a duplicate task, i.e., a user can only have one task called "Sweep the floor."

    • Users do not share tasks. For instance, if two users have a task "Sweep the floor.", there should be two tasks with the summary "Sweep the floor." on the backend, one for each of the two users

    • I cannot add a user field on the Task model - I have to assign ownership of Task objects via permissions


    Out of the box, the django_guardian UserObjectPermission has this unique_together constraint:



    unique_together = ['user', 'permission', 'object_pk']


    I think what I am looking for is a unique_together constraint that is more like this pseudo-code:



    unique_together = ['user', 'permission', 'object_pk', 'task__summary']


    Or, is there another way to enforce this type of uniqueness at the database level using Django Guardian permissions?










    share|improve this question

























      0












      0








      0








      Using the example from the docs, let's assume I have a Task model:



      class Task(models.Model):
      summary = models.CharField(max_length=32)
      content = models.TextField()
      reported_by = models.ForeignKey(User, on_delete=models.CASCADE)
      created_at = models.DateTimeField(auto_now_add=True)

      class Meta:
      permissions = (
      ('view_task', 'View task'),
      )


      Let's say I have many users on my app, and I want to make sure of the following at the database level:




      • No user has a duplicate task, i.e., a user can only have one task called "Sweep the floor."

      • Users do not share tasks. For instance, if two users have a task "Sweep the floor.", there should be two tasks with the summary "Sweep the floor." on the backend, one for each of the two users

      • I cannot add a user field on the Task model - I have to assign ownership of Task objects via permissions


      Out of the box, the django_guardian UserObjectPermission has this unique_together constraint:



      unique_together = ['user', 'permission', 'object_pk']


      I think what I am looking for is a unique_together constraint that is more like this pseudo-code:



      unique_together = ['user', 'permission', 'object_pk', 'task__summary']


      Or, is there another way to enforce this type of uniqueness at the database level using Django Guardian permissions?










      share|improve this question














      Using the example from the docs, let's assume I have a Task model:



      class Task(models.Model):
      summary = models.CharField(max_length=32)
      content = models.TextField()
      reported_by = models.ForeignKey(User, on_delete=models.CASCADE)
      created_at = models.DateTimeField(auto_now_add=True)

      class Meta:
      permissions = (
      ('view_task', 'View task'),
      )


      Let's say I have many users on my app, and I want to make sure of the following at the database level:




      • No user has a duplicate task, i.e., a user can only have one task called "Sweep the floor."

      • Users do not share tasks. For instance, if two users have a task "Sweep the floor.", there should be two tasks with the summary "Sweep the floor." on the backend, one for each of the two users

      • I cannot add a user field on the Task model - I have to assign ownership of Task objects via permissions


      Out of the box, the django_guardian UserObjectPermission has this unique_together constraint:



      unique_together = ['user', 'permission', 'object_pk']


      I think what I am looking for is a unique_together constraint that is more like this pseudo-code:



      unique_together = ['user', 'permission', 'object_pk', 'task__summary']


      Or, is there another way to enforce this type of uniqueness at the database level using Django Guardian permissions?







      django django-guardian






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 2 at 19:32









      YPCrumbleYPCrumble

      10.1k965119




      10.1k965119
























          0






          active

          oldest

          votes












          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%2f54012146%2fhow-can-i-add-an-additional-unique-together-constraint-to-django-guardian-object%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54012146%2fhow-can-i-add-an-additional-unique-together-constraint-to-django-guardian-object%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

          'app-layout' is not a known element: how to share Component with different Modules

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          WPF add header to Image with URL pettitions [duplicate]