SQL — temporarily snapshotting/archiving a query across Flask pages












0















I want to temporarily save information from one query across multiple flask routes.



Basically, I have a function solely for queries. I use a query to fetch a random id. Using this id, I gather all other information needed for this instance. It is then used in route1 (I call it here through a dictionary). The user inputs something and then all of the info is transferred to route2 using "url_for".



The program is messing up because instead of using the same id for both routes, route2 is querying again and using a different set of information based on a different id. I want the id to stay the same for both routes. I want it to change everytime route1 is refreshed or visited, but otherwise stay the same.



Let me know any thoughts or ideas!



def get_db():
random_id = db.execute("SELECT id FROM list ORDER BY RANDOM() LIMIT 1").fetchone()[0]

score = query to select score using {random_id}
image = quesry to select score using {random_id}
info = {
'random_id': random_id,
'image': image,
'score': score
}
return info

@app.route('route1')
data=det_db():
def functionA():
uses data.get() to call information from query in dictionary
return redirect(url_for('fucntionB', random_id=random_id, image=image, score=score))

@app.route('route2')
def functionB():
info=request.args
random_id=info.get('random_id')
image=info.get('image')
score=info.get('score')









share|improve this question



























    0















    I want to temporarily save information from one query across multiple flask routes.



    Basically, I have a function solely for queries. I use a query to fetch a random id. Using this id, I gather all other information needed for this instance. It is then used in route1 (I call it here through a dictionary). The user inputs something and then all of the info is transferred to route2 using "url_for".



    The program is messing up because instead of using the same id for both routes, route2 is querying again and using a different set of information based on a different id. I want the id to stay the same for both routes. I want it to change everytime route1 is refreshed or visited, but otherwise stay the same.



    Let me know any thoughts or ideas!



    def get_db():
    random_id = db.execute("SELECT id FROM list ORDER BY RANDOM() LIMIT 1").fetchone()[0]

    score = query to select score using {random_id}
    image = quesry to select score using {random_id}
    info = {
    'random_id': random_id,
    'image': image,
    'score': score
    }
    return info

    @app.route('route1')
    data=det_db():
    def functionA():
    uses data.get() to call information from query in dictionary
    return redirect(url_for('fucntionB', random_id=random_id, image=image, score=score))

    @app.route('route2')
    def functionB():
    info=request.args
    random_id=info.get('random_id')
    image=info.get('image')
    score=info.get('score')









    share|improve this question

























      0












      0








      0








      I want to temporarily save information from one query across multiple flask routes.



      Basically, I have a function solely for queries. I use a query to fetch a random id. Using this id, I gather all other information needed for this instance. It is then used in route1 (I call it here through a dictionary). The user inputs something and then all of the info is transferred to route2 using "url_for".



      The program is messing up because instead of using the same id for both routes, route2 is querying again and using a different set of information based on a different id. I want the id to stay the same for both routes. I want it to change everytime route1 is refreshed or visited, but otherwise stay the same.



      Let me know any thoughts or ideas!



      def get_db():
      random_id = db.execute("SELECT id FROM list ORDER BY RANDOM() LIMIT 1").fetchone()[0]

      score = query to select score using {random_id}
      image = quesry to select score using {random_id}
      info = {
      'random_id': random_id,
      'image': image,
      'score': score
      }
      return info

      @app.route('route1')
      data=det_db():
      def functionA():
      uses data.get() to call information from query in dictionary
      return redirect(url_for('fucntionB', random_id=random_id, image=image, score=score))

      @app.route('route2')
      def functionB():
      info=request.args
      random_id=info.get('random_id')
      image=info.get('image')
      score=info.get('score')









      share|improve this question














      I want to temporarily save information from one query across multiple flask routes.



      Basically, I have a function solely for queries. I use a query to fetch a random id. Using this id, I gather all other information needed for this instance. It is then used in route1 (I call it here through a dictionary). The user inputs something and then all of the info is transferred to route2 using "url_for".



      The program is messing up because instead of using the same id for both routes, route2 is querying again and using a different set of information based on a different id. I want the id to stay the same for both routes. I want it to change everytime route1 is refreshed or visited, but otherwise stay the same.



      Let me know any thoughts or ideas!



      def get_db():
      random_id = db.execute("SELECT id FROM list ORDER BY RANDOM() LIMIT 1").fetchone()[0]

      score = query to select score using {random_id}
      image = quesry to select score using {random_id}
      info = {
      'random_id': random_id,
      'image': image,
      'score': score
      }
      return info

      @app.route('route1')
      data=det_db():
      def functionA():
      uses data.get() to call information from query in dictionary
      return redirect(url_for('fucntionB', random_id=random_id, image=image, score=score))

      @app.route('route2')
      def functionB():
      info=request.args
      random_id=info.get('random_id')
      image=info.get('image')
      score=info.get('score')






      python sql flask






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 21:56









      MadelineKinnairdMadelineKinnaird

      234




      234
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Have you looked into local storage? Perhaps you could store the id in local storage when route1 is hit, and then access it when route2 is hit.



          <script>
          localstorage.setItem('name', 'value')
          </script>

          <script>
          var item = localStorage.getItem('name');
          </script>


          These two scripts will allow you to store and retrieve from local storage.






          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%2f53421026%2fsql-temporarily-snapshotting-archiving-a-query-across-flask-pages%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














            Have you looked into local storage? Perhaps you could store the id in local storage when route1 is hit, and then access it when route2 is hit.



            <script>
            localstorage.setItem('name', 'value')
            </script>

            <script>
            var item = localStorage.getItem('name');
            </script>


            These two scripts will allow you to store and retrieve from local storage.






            share|improve this answer




























              0














              Have you looked into local storage? Perhaps you could store the id in local storage when route1 is hit, and then access it when route2 is hit.



              <script>
              localstorage.setItem('name', 'value')
              </script>

              <script>
              var item = localStorage.getItem('name');
              </script>


              These two scripts will allow you to store and retrieve from local storage.






              share|improve this answer


























                0












                0








                0







                Have you looked into local storage? Perhaps you could store the id in local storage when route1 is hit, and then access it when route2 is hit.



                <script>
                localstorage.setItem('name', 'value')
                </script>

                <script>
                var item = localStorage.getItem('name');
                </script>


                These two scripts will allow you to store and retrieve from local storage.






                share|improve this answer













                Have you looked into local storage? Perhaps you could store the id in local storage when route1 is hit, and then access it when route2 is hit.



                <script>
                localstorage.setItem('name', 'value')
                </script>

                <script>
                var item = localStorage.getItem('name');
                </script>


                These two scripts will allow you to store and retrieve from local storage.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 21 '18 at 23:28









                Landon MarshallLandon Marshall

                198




                198
































                    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%2f53421026%2fsql-temporarily-snapshotting-archiving-a-query-across-flask-pages%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

                    MongoDB - Not Authorized To Execute Command

                    How to fix TextFormField cause rebuild widget in Flutter

                    in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith