Handling Attributes containing foreign key in EAV db modelling












0















I am trying to implement taxation feature for my e-commerce app.
The tax has some general configuration values like, tax_country, shipping_tax, label etc.



Since these values can change in future I am using Entity Attribute Value modeling.



I have seen the approach from the following blog.



So I have the following tables:





  • Entity: contains all the entities.


  • Attribute: contains attributes for entities.


  • Metadata: contains some metadata for attributes common to all attributes.

  • For every data type, I will have different tables which will store values for the attributesattribute_value_int, attribute_value_char etc.


So attributes are stored in the respective attribute_value table.



However, there are some attributes which are like foreign keys.
e.g. tax_country attribute contains the id of the country from the country table.



How should I go about handling attributes which are basically relationships with other tables?










share|improve this question



























    0















    I am trying to implement taxation feature for my e-commerce app.
    The tax has some general configuration values like, tax_country, shipping_tax, label etc.



    Since these values can change in future I am using Entity Attribute Value modeling.



    I have seen the approach from the following blog.



    So I have the following tables:





    • Entity: contains all the entities.


    • Attribute: contains attributes for entities.


    • Metadata: contains some metadata for attributes common to all attributes.

    • For every data type, I will have different tables which will store values for the attributesattribute_value_int, attribute_value_char etc.


    So attributes are stored in the respective attribute_value table.



    However, there are some attributes which are like foreign keys.
    e.g. tax_country attribute contains the id of the country from the country table.



    How should I go about handling attributes which are basically relationships with other tables?










    share|improve this question

























      0












      0








      0








      I am trying to implement taxation feature for my e-commerce app.
      The tax has some general configuration values like, tax_country, shipping_tax, label etc.



      Since these values can change in future I am using Entity Attribute Value modeling.



      I have seen the approach from the following blog.



      So I have the following tables:





      • Entity: contains all the entities.


      • Attribute: contains attributes for entities.


      • Metadata: contains some metadata for attributes common to all attributes.

      • For every data type, I will have different tables which will store values for the attributesattribute_value_int, attribute_value_char etc.


      So attributes are stored in the respective attribute_value table.



      However, there are some attributes which are like foreign keys.
      e.g. tax_country attribute contains the id of the country from the country table.



      How should I go about handling attributes which are basically relationships with other tables?










      share|improve this question














      I am trying to implement taxation feature for my e-commerce app.
      The tax has some general configuration values like, tax_country, shipping_tax, label etc.



      Since these values can change in future I am using Entity Attribute Value modeling.



      I have seen the approach from the following blog.



      So I have the following tables:





      • Entity: contains all the entities.


      • Attribute: contains attributes for entities.


      • Metadata: contains some metadata for attributes common to all attributes.

      • For every data type, I will have different tables which will store values for the attributesattribute_value_int, attribute_value_char etc.


      So attributes are stored in the respective attribute_value table.



      However, there are some attributes which are like foreign keys.
      e.g. tax_country attribute contains the id of the country from the country table.



      How should I go about handling attributes which are basically relationships with other tables?







      database postgresql entity-attribute-value






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 days ago









      Arjun SinghArjun Singh

      384211




      384211
























          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%2f54252570%2fhandling-attributes-containing-foreign-key-in-eav-db-modelling%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%2f54252570%2fhandling-attributes-containing-foreign-key-in-eav-db-modelling%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

          Callistus III

          Plistias Cous

          Index Sanctorum