How to hold different data with several same fields?












0















We want to store information about bank's credits but this information changes from bank to bank (for some banks user's id is important for others not). We are going to create one huge table and store all values from all banks there. Is for some bank fields is mandatory we will store actual value on the other hand if this field does not mean much we will store default value. But we see another way out, to create many small tables for each bank, but this decision seems to be very difficult to handle in the feature.
Could you give an advise










share|improve this question





























    0















    We want to store information about bank's credits but this information changes from bank to bank (for some banks user's id is important for others not). We are going to create one huge table and store all values from all banks there. Is for some bank fields is mandatory we will store actual value on the other hand if this field does not mean much we will store default value. But we see another way out, to create many small tables for each bank, but this decision seems to be very difficult to handle in the feature.
    Could you give an advise










    share|improve this question



























      0












      0








      0








      We want to store information about bank's credits but this information changes from bank to bank (for some banks user's id is important for others not). We are going to create one huge table and store all values from all banks there. Is for some bank fields is mandatory we will store actual value on the other hand if this field does not mean much we will store default value. But we see another way out, to create many small tables for each bank, but this decision seems to be very difficult to handle in the feature.
      Could you give an advise










      share|improve this question
















      We want to store information about bank's credits but this information changes from bank to bank (for some banks user's id is important for others not). We are going to create one huge table and store all values from all banks there. Is for some bank fields is mandatory we will store actual value on the other hand if this field does not mean much we will store default value. But we see another way out, to create many small tables for each bank, but this decision seems to be very difficult to handle in the feature.
      Could you give an advise







      database-design relational-database






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 19 '18 at 15:48









      a_horse_with_no_name

      297k46452547




      297k46452547










      asked Nov 19 '18 at 14:52









      GGGGGG

      5717




      5717
























          1 Answer
          1






          active

          oldest

          votes


















          1














          You need to create one table having a bank_id column as a discriminator.
          However, if the table is expected to be really huge (hundred of millions rows) you still can optimize the queries which affect only one bank: the solution is the table partitioning on the same column bank_id.






          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%2f53377165%2fhow-to-hold-different-data-with-several-same-fields%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









            1














            You need to create one table having a bank_id column as a discriminator.
            However, if the table is expected to be really huge (hundred of millions rows) you still can optimize the queries which affect only one bank: the solution is the table partitioning on the same column bank_id.






            share|improve this answer






























              1














              You need to create one table having a bank_id column as a discriminator.
              However, if the table is expected to be really huge (hundred of millions rows) you still can optimize the queries which affect only one bank: the solution is the table partitioning on the same column bank_id.






              share|improve this answer




























                1












                1








                1







                You need to create one table having a bank_id column as a discriminator.
                However, if the table is expected to be really huge (hundred of millions rows) you still can optimize the queries which affect only one bank: the solution is the table partitioning on the same column bank_id.






                share|improve this answer















                You need to create one table having a bank_id column as a discriminator.
                However, if the table is expected to be really huge (hundred of millions rows) you still can optimize the queries which affect only one bank: the solution is the table partitioning on the same column bank_id.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 19 '18 at 15:53

























                answered Nov 19 '18 at 15:45









                sergeserge

                60047




                60047






























                    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%2f53377165%2fhow-to-hold-different-data-with-several-same-fields%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

                    Guess what letter conforming each word

                    Run scheduled task as local user group (not BUILTIN)

                    Port of Spain