Abstract or generic django class inheritance?












0















I want to be able to get the list of all wallets in my app - but every wallet needs to be specified as UserWallet, TeamWallet, CarWallet, and so on. There should be no generic wallet instances. I still want to be able to set foreign keys in other models (eg payment model) to the generic wallet model or link in a way to the wallet without having one foreign key for each child model.



I see these advantages for generic class inheritance:




  • I can get a list of all wallets

  • I can set foreign keys to the parent wallet model


Disadvantages for the generic class inheritance:




  • I can't make prohibit creating a generic wallet inheritance.

  • Slower cause of JOIN in database

  • Confusing DB structure


I see these advantages of using abstract class inheritance:




  • No generic wallet instances possible.

  • Easy database table structure.


Disadvantages for the abstract class inheritance:




  • I need to use itertools or other hacks to get a list of all wallets.

  • I need to set up one foreign key for each child model in outside models, or use slow contenttype keys.


As I am pretty new to Python and Django development, I think I'm misssing quite some points. How do you solve these situations?



Example mockup structure:



class Wallet(models.Model):
status = models.CharField(max_length=10)
is_default = models.NullBooleanField()

class UserWallet(Wallet):
user = models.ForeignKey(User, on_delete=models.CASCADE)

class TeamWallet(Wallet):
team = models.ForeignKey(Team, on_delete=models.CASCADE)


class Payment(models.Model):
wallet = models.ForeignKey(Wallet, on_delete=models.CASCADE)


Thanks for your help and any thought.










share|improve this question





























    0















    I want to be able to get the list of all wallets in my app - but every wallet needs to be specified as UserWallet, TeamWallet, CarWallet, and so on. There should be no generic wallet instances. I still want to be able to set foreign keys in other models (eg payment model) to the generic wallet model or link in a way to the wallet without having one foreign key for each child model.



    I see these advantages for generic class inheritance:




    • I can get a list of all wallets

    • I can set foreign keys to the parent wallet model


    Disadvantages for the generic class inheritance:




    • I can't make prohibit creating a generic wallet inheritance.

    • Slower cause of JOIN in database

    • Confusing DB structure


    I see these advantages of using abstract class inheritance:




    • No generic wallet instances possible.

    • Easy database table structure.


    Disadvantages for the abstract class inheritance:




    • I need to use itertools or other hacks to get a list of all wallets.

    • I need to set up one foreign key for each child model in outside models, or use slow contenttype keys.


    As I am pretty new to Python and Django development, I think I'm misssing quite some points. How do you solve these situations?



    Example mockup structure:



    class Wallet(models.Model):
    status = models.CharField(max_length=10)
    is_default = models.NullBooleanField()

    class UserWallet(Wallet):
    user = models.ForeignKey(User, on_delete=models.CASCADE)

    class TeamWallet(Wallet):
    team = models.ForeignKey(Team, on_delete=models.CASCADE)


    class Payment(models.Model):
    wallet = models.ForeignKey(Wallet, on_delete=models.CASCADE)


    Thanks for your help and any thought.










    share|improve this question



























      0












      0








      0








      I want to be able to get the list of all wallets in my app - but every wallet needs to be specified as UserWallet, TeamWallet, CarWallet, and so on. There should be no generic wallet instances. I still want to be able to set foreign keys in other models (eg payment model) to the generic wallet model or link in a way to the wallet without having one foreign key for each child model.



      I see these advantages for generic class inheritance:




      • I can get a list of all wallets

      • I can set foreign keys to the parent wallet model


      Disadvantages for the generic class inheritance:




      • I can't make prohibit creating a generic wallet inheritance.

      • Slower cause of JOIN in database

      • Confusing DB structure


      I see these advantages of using abstract class inheritance:




      • No generic wallet instances possible.

      • Easy database table structure.


      Disadvantages for the abstract class inheritance:




      • I need to use itertools or other hacks to get a list of all wallets.

      • I need to set up one foreign key for each child model in outside models, or use slow contenttype keys.


      As I am pretty new to Python and Django development, I think I'm misssing quite some points. How do you solve these situations?



      Example mockup structure:



      class Wallet(models.Model):
      status = models.CharField(max_length=10)
      is_default = models.NullBooleanField()

      class UserWallet(Wallet):
      user = models.ForeignKey(User, on_delete=models.CASCADE)

      class TeamWallet(Wallet):
      team = models.ForeignKey(Team, on_delete=models.CASCADE)


      class Payment(models.Model):
      wallet = models.ForeignKey(Wallet, on_delete=models.CASCADE)


      Thanks for your help and any thought.










      share|improve this question
















      I want to be able to get the list of all wallets in my app - but every wallet needs to be specified as UserWallet, TeamWallet, CarWallet, and so on. There should be no generic wallet instances. I still want to be able to set foreign keys in other models (eg payment model) to the generic wallet model or link in a way to the wallet without having one foreign key for each child model.



      I see these advantages for generic class inheritance:




      • I can get a list of all wallets

      • I can set foreign keys to the parent wallet model


      Disadvantages for the generic class inheritance:




      • I can't make prohibit creating a generic wallet inheritance.

      • Slower cause of JOIN in database

      • Confusing DB structure


      I see these advantages of using abstract class inheritance:




      • No generic wallet instances possible.

      • Easy database table structure.


      Disadvantages for the abstract class inheritance:




      • I need to use itertools or other hacks to get a list of all wallets.

      • I need to set up one foreign key for each child model in outside models, or use slow contenttype keys.


      As I am pretty new to Python and Django development, I think I'm misssing quite some points. How do you solve these situations?



      Example mockup structure:



      class Wallet(models.Model):
      status = models.CharField(max_length=10)
      is_default = models.NullBooleanField()

      class UserWallet(Wallet):
      user = models.ForeignKey(User, on_delete=models.CASCADE)

      class TeamWallet(Wallet):
      team = models.ForeignKey(Team, on_delete=models.CASCADE)


      class Payment(models.Model):
      wallet = models.ForeignKey(Wallet, on_delete=models.CASCADE)


      Thanks for your help and any thought.







      django class inheritance abstract-class






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '18 at 13:31







      LGG

















      asked Nov 14 '18 at 13:25









      LGGLGG

      314




      314
























          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%2f53301302%2fabstract-or-generic-django-class-inheritance%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%2f53301302%2fabstract-or-generic-django-class-inheritance%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

          Xamarin.iOS Cant Deploy on Iphone

          Glorious Revolution

          Dulmage-Mendelsohn matrix decomposition in Python