How do I persist data in custom table in Magento Database (the right way)?












1















I have created a module that adds a custom table.



I also created a Model, ResourceModel and Collection classes, and was able to use them to insert data into this new table by calling the ModelFactory class and saving (save()) the data.



But I am wondering if this is the best practice or if I should create Api interfaces for doing that, or/and using Service Contract even if I don't want this class in Magento API.










share|improve this question





























    1















    I have created a module that adds a custom table.



    I also created a Model, ResourceModel and Collection classes, and was able to use them to insert data into this new table by calling the ModelFactory class and saving (save()) the data.



    But I am wondering if this is the best practice or if I should create Api interfaces for doing that, or/and using Service Contract even if I don't want this class in Magento API.










    share|improve this question



























      1












      1








      1








      I have created a module that adds a custom table.



      I also created a Model, ResourceModel and Collection classes, and was able to use them to insert data into this new table by calling the ModelFactory class and saving (save()) the data.



      But I am wondering if this is the best practice or if I should create Api interfaces for doing that, or/and using Service Contract even if I don't want this class in Magento API.










      share|improve this question
















      I have created a module that adds a custom table.



      I also created a Model, ResourceModel and Collection classes, and was able to use them to insert data into this new table by calling the ModelFactory class and saving (save()) the data.



      But I am wondering if this is the best practice or if I should create Api interfaces for doing that, or/and using Service Contract even if I don't want this class in Magento API.







      magento2 service-contract






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 1 hour ago









      Taran

      464312




      464312










      asked 3 hours ago









      Ricardo MartinsRicardo Martins

      600420




      600420






















          1 Answer
          1






          active

          oldest

          votes


















          0














          You need:




          1. Resource Model for CRUD operations

          2. Model/ModelInterface for Data Modeling

          3. Repository/RepositoryInterface as frontend for database operations

          4. Custom table


          Technically, you don't need interfaces but it is best practice and there is a reason behind it.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "479"
            };
            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: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            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%2fmagento.stackexchange.com%2fquestions%2f262142%2fhow-do-i-persist-data-in-custom-table-in-magento-database-the-right-way%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














            You need:




            1. Resource Model for CRUD operations

            2. Model/ModelInterface for Data Modeling

            3. Repository/RepositoryInterface as frontend for database operations

            4. Custom table


            Technically, you don't need interfaces but it is best practice and there is a reason behind it.






            share|improve this answer




























              0














              You need:




              1. Resource Model for CRUD operations

              2. Model/ModelInterface for Data Modeling

              3. Repository/RepositoryInterface as frontend for database operations

              4. Custom table


              Technically, you don't need interfaces but it is best practice and there is a reason behind it.






              share|improve this answer


























                0












                0








                0







                You need:




                1. Resource Model for CRUD operations

                2. Model/ModelInterface for Data Modeling

                3. Repository/RepositoryInterface as frontend for database operations

                4. Custom table


                Technically, you don't need interfaces but it is best practice and there is a reason behind it.






                share|improve this answer













                You need:




                1. Resource Model for CRUD operations

                2. Model/ModelInterface for Data Modeling

                3. Repository/RepositoryInterface as frontend for database operations

                4. Custom table


                Technically, you don't need interfaces but it is best practice and there is a reason behind it.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 2 hours ago









                Shawn AbramsonShawn Abramson

                2,4771915




                2,4771915






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Magento Stack Exchange!


                    • 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%2fmagento.stackexchange.com%2fquestions%2f262142%2fhow-do-i-persist-data-in-custom-table-in-magento-database-the-right-way%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

                    Polycentropodidae

                    Magento 2 Error message: Invalid state change requested

                    Paulmy