What are persisted objects called in an MVC application?












0















If you persist data in a relational database and use the MVC or HMVC architectures, would a table correspond to a model? If not, what would you call that type of object? I've been hearing debates where some people call them domain objects and others don't differentiate the two.










share|improve this question





























    0















    If you persist data in a relational database and use the MVC or HMVC architectures, would a table correspond to a model? If not, what would you call that type of object? I've been hearing debates where some people call them domain objects and others don't differentiate the two.










    share|improve this question



























      0












      0








      0








      If you persist data in a relational database and use the MVC or HMVC architectures, would a table correspond to a model? If not, what would you call that type of object? I've been hearing debates where some people call them domain objects and others don't differentiate the two.










      share|improve this question
















      If you persist data in a relational database and use the MVC or HMVC architectures, would a table correspond to a model? If not, what would you call that type of object? I've been hearing debates where some people call them domain objects and others don't differentiate the two.







      model-view-controller naming






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 26 '18 at 16:29









      jaco0646

      5,41452947




      5,41452947










      asked Nov 23 '18 at 1:05









      Pier-Luc WhissellPier-Luc Whissell

      665




      665
























          1 Answer
          1






          active

          oldest

          votes


















          0















          I've been hereing debates where some people call them domain objects and others don't defferenciate the two




          --> That's because this doesn't matter at all. Domain eg. from mathematics can be seen as the model because it defines the data type, range, complexity, ... = the set of possible values for your logic or function. This is mostly identical to a model. In addition to that this does not change anything to call them domain objects or model entities or whatever. The Model (in MVC world) is a concept. The way you define/implement your model is completely up to you as soon as you maintain the separation with the other layers and fits the concept.






          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%2f53439570%2fwhat-are-persisted-objects-called-in-an-mvc-application%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















            I've been hereing debates where some people call them domain objects and others don't defferenciate the two




            --> That's because this doesn't matter at all. Domain eg. from mathematics can be seen as the model because it defines the data type, range, complexity, ... = the set of possible values for your logic or function. This is mostly identical to a model. In addition to that this does not change anything to call them domain objects or model entities or whatever. The Model (in MVC world) is a concept. The way you define/implement your model is completely up to you as soon as you maintain the separation with the other layers and fits the concept.






            share|improve this answer




























              0















              I've been hereing debates where some people call them domain objects and others don't defferenciate the two




              --> That's because this doesn't matter at all. Domain eg. from mathematics can be seen as the model because it defines the data type, range, complexity, ... = the set of possible values for your logic or function. This is mostly identical to a model. In addition to that this does not change anything to call them domain objects or model entities or whatever. The Model (in MVC world) is a concept. The way you define/implement your model is completely up to you as soon as you maintain the separation with the other layers and fits the concept.






              share|improve this answer


























                0












                0








                0








                I've been hereing debates where some people call them domain objects and others don't defferenciate the two




                --> That's because this doesn't matter at all. Domain eg. from mathematics can be seen as the model because it defines the data type, range, complexity, ... = the set of possible values for your logic or function. This is mostly identical to a model. In addition to that this does not change anything to call them domain objects or model entities or whatever. The Model (in MVC world) is a concept. The way you define/implement your model is completely up to you as soon as you maintain the separation with the other layers and fits the concept.






                share|improve this answer














                I've been hereing debates where some people call them domain objects and others don't defferenciate the two




                --> That's because this doesn't matter at all. Domain eg. from mathematics can be seen as the model because it defines the data type, range, complexity, ... = the set of possible values for your logic or function. This is mostly identical to a model. In addition to that this does not change anything to call them domain objects or model entities or whatever. The Model (in MVC world) is a concept. The way you define/implement your model is completely up to you as soon as you maintain the separation with the other layers and fits the concept.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 23 '18 at 1:36









                bsaverinobsaverino

                20917




                20917
































                    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%2f53439570%2fwhat-are-persisted-objects-called-in-an-mvc-application%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

                    "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                    Alcedinidae

                    RAC Tourist Trophy