play-slick scala many to many












0















I have an endpoint lets say /order/ where i can send json object(my order), which contains some products etc, so my problem is i have to first save the order and wait for the order id back from the db and then save my products with this new order id( we are talking many to many relation thats why theres another table)



Consider this controller method



def postOrder = Action(parse.json[OrderRest]) { req => {

Created(Json.toJson(manageOrderService.insertOrder(req.body)))
}
}


this is how my repo methods look like



  def addOrder(order: Order) = db.run {
(orders returning orders) += order
}


how can i chain db.runs to first insert order, get order id and then insert my products with this order id i just got?



im thinking about putting some service between my controller and repo, and managing those actions there, but i have no idea where to start










share|improve this question



























    0















    I have an endpoint lets say /order/ where i can send json object(my order), which contains some products etc, so my problem is i have to first save the order and wait for the order id back from the db and then save my products with this new order id( we are talking many to many relation thats why theres another table)



    Consider this controller method



    def postOrder = Action(parse.json[OrderRest]) { req => {

    Created(Json.toJson(manageOrderService.insertOrder(req.body)))
    }
    }


    this is how my repo methods look like



      def addOrder(order: Order) = db.run {
    (orders returning orders) += order
    }


    how can i chain db.runs to first insert order, get order id and then insert my products with this order id i just got?



    im thinking about putting some service between my controller and repo, and managing those actions there, but i have no idea where to start










    share|improve this question

























      0












      0








      0








      I have an endpoint lets say /order/ where i can send json object(my order), which contains some products etc, so my problem is i have to first save the order and wait for the order id back from the db and then save my products with this new order id( we are talking many to many relation thats why theres another table)



      Consider this controller method



      def postOrder = Action(parse.json[OrderRest]) { req => {

      Created(Json.toJson(manageOrderService.insertOrder(req.body)))
      }
      }


      this is how my repo methods look like



        def addOrder(order: Order) = db.run {
      (orders returning orders) += order
      }


      how can i chain db.runs to first insert order, get order id and then insert my products with this order id i just got?



      im thinking about putting some service between my controller and repo, and managing those actions there, but i have no idea where to start










      share|improve this question














      I have an endpoint lets say /order/ where i can send json object(my order), which contains some products etc, so my problem is i have to first save the order and wait for the order id back from the db and then save my products with this new order id( we are talking many to many relation thats why theres another table)



      Consider this controller method



      def postOrder = Action(parse.json[OrderRest]) { req => {

      Created(Json.toJson(manageOrderService.insertOrder(req.body)))
      }
      }


      this is how my repo methods look like



        def addOrder(order: Order) = db.run {
      (orders returning orders) += order
      }


      how can i chain db.runs to first insert order, get order id and then insert my products with this order id i just got?



      im thinking about putting some service between my controller and repo, and managing those actions there, but i have no idea where to start







      sql scala many-to-many slick






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 26 '18 at 8:03









      adamblumsteinadamblumstein

      204




      204
























          1 Answer
          1






          active

          oldest

          votes


















          0














          You can use for to chain database operations. Here is an example of adding a table to a db by adding a header row to represent the table and then adding the data rows. In this case it is a simple table containing (age, value).



          /** Add a new table to the database */
          def addTable(name: String, table: Seq[(Int, Int)]) = {
          val action = for {
          key <- (Headers returning Headers.map(_.tableId)) += HeadersRow(0, name)
          _ <- Values ++= table.map { case (age, value) => ValuesRow(key, age, value) }
          } yield key

          db.run(action.transactionally)
          }


          This is cut down from the working code, but it should give the idea of how to do what you want. The first for statement would generate the order id and then the second statement would add the order with that order id.



          This is done transactionally so that the new order will not be created unless the order data is valid (in database terms).






          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%2f53476855%2fplay-slick-scala-many-to-many%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 can use for to chain database operations. Here is an example of adding a table to a db by adding a header row to represent the table and then adding the data rows. In this case it is a simple table containing (age, value).



            /** Add a new table to the database */
            def addTable(name: String, table: Seq[(Int, Int)]) = {
            val action = for {
            key <- (Headers returning Headers.map(_.tableId)) += HeadersRow(0, name)
            _ <- Values ++= table.map { case (age, value) => ValuesRow(key, age, value) }
            } yield key

            db.run(action.transactionally)
            }


            This is cut down from the working code, but it should give the idea of how to do what you want. The first for statement would generate the order id and then the second statement would add the order with that order id.



            This is done transactionally so that the new order will not be created unless the order data is valid (in database terms).






            share|improve this answer




























              0














              You can use for to chain database operations. Here is an example of adding a table to a db by adding a header row to represent the table and then adding the data rows. In this case it is a simple table containing (age, value).



              /** Add a new table to the database */
              def addTable(name: String, table: Seq[(Int, Int)]) = {
              val action = for {
              key <- (Headers returning Headers.map(_.tableId)) += HeadersRow(0, name)
              _ <- Values ++= table.map { case (age, value) => ValuesRow(key, age, value) }
              } yield key

              db.run(action.transactionally)
              }


              This is cut down from the working code, but it should give the idea of how to do what you want. The first for statement would generate the order id and then the second statement would add the order with that order id.



              This is done transactionally so that the new order will not be created unless the order data is valid (in database terms).






              share|improve this answer


























                0












                0








                0







                You can use for to chain database operations. Here is an example of adding a table to a db by adding a header row to represent the table and then adding the data rows. In this case it is a simple table containing (age, value).



                /** Add a new table to the database */
                def addTable(name: String, table: Seq[(Int, Int)]) = {
                val action = for {
                key <- (Headers returning Headers.map(_.tableId)) += HeadersRow(0, name)
                _ <- Values ++= table.map { case (age, value) => ValuesRow(key, age, value) }
                } yield key

                db.run(action.transactionally)
                }


                This is cut down from the working code, but it should give the idea of how to do what you want. The first for statement would generate the order id and then the second statement would add the order with that order id.



                This is done transactionally so that the new order will not be created unless the order data is valid (in database terms).






                share|improve this answer













                You can use for to chain database operations. Here is an example of adding a table to a db by adding a header row to represent the table and then adding the data rows. In this case it is a simple table containing (age, value).



                /** Add a new table to the database */
                def addTable(name: String, table: Seq[(Int, Int)]) = {
                val action = for {
                key <- (Headers returning Headers.map(_.tableId)) += HeadersRow(0, name)
                _ <- Values ++= table.map { case (age, value) => ValuesRow(key, age, value) }
                } yield key

                db.run(action.transactionally)
                }


                This is cut down from the working code, but it should give the idea of how to do what you want. The first for statement would generate the order id and then the second statement would add the order with that order id.



                This is done transactionally so that the new order will not be created unless the order data is valid (in database terms).







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 26 '18 at 10:01









                TimTim

                5,7431617




                5,7431617
































                    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%2f53476855%2fplay-slick-scala-many-to-many%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

                    Lallio

                    Futebolista

                    Jornalista