How do I know which fields are indexed in pouchdb if I use query() API?












0














I am new to pouchdb and I am reading below source code:



                    db.query('product_index', {
startkey: ["01234"],
endkey: ["01234", {}],
include_docs: false
});


this code executes for a long time. After read some pouchdb document it looks like it builds index on the database when it run the first time. But I don't understand which fields are indexed based on above code.



Below code I can see it builds index on field foo. But how can I understand query API for building index? What is the different between using query and createIndex from index perceptive?



db.createIndex({
index: {
fields: ['foo']
}
})









share|improve this question



























    0














    I am new to pouchdb and I am reading below source code:



                        db.query('product_index', {
    startkey: ["01234"],
    endkey: ["01234", {}],
    include_docs: false
    });


    this code executes for a long time. After read some pouchdb document it looks like it builds index on the database when it run the first time. But I don't understand which fields are indexed based on above code.



    Below code I can see it builds index on field foo. But how can I understand query API for building index? What is the different between using query and createIndex from index perceptive?



    db.createIndex({
    index: {
    fields: ['foo']
    }
    })









    share|improve this question

























      0












      0








      0







      I am new to pouchdb and I am reading below source code:



                          db.query('product_index', {
      startkey: ["01234"],
      endkey: ["01234", {}],
      include_docs: false
      });


      this code executes for a long time. After read some pouchdb document it looks like it builds index on the database when it run the first time. But I don't understand which fields are indexed based on above code.



      Below code I can see it builds index on field foo. But how can I understand query API for building index? What is the different between using query and createIndex from index perceptive?



      db.createIndex({
      index: {
      fields: ['foo']
      }
      })









      share|improve this question













      I am new to pouchdb and I am reading below source code:



                          db.query('product_index', {
      startkey: ["01234"],
      endkey: ["01234", {}],
      include_docs: false
      });


      this code executes for a long time. After read some pouchdb document it looks like it builds index on the database when it run the first time. But I don't understand which fields are indexed based on above code.



      Below code I can see it builds index on field foo. But how can I understand query API for building index? What is the different between using query and createIndex from index perceptive?



      db.createIndex({
      index: {
      fields: ['foo']
      }
      })






      couchdb pouchdb






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '18 at 9:55









      Zhao YiZhao Yi

      5,3061451121




      5,3061451121
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Have you seen the PouchDB Guide Bulk operations section Please use 'allDocs()'. Seriously.?




          Far too many developers overlook this valuable API, because they
          misunderstand it. When a developer says "my PouchDB app is slow!", it
          is usually because they are using the slow query() API when they
          should be using the fast allDocs() API.




          When designing your data structures it's very important to bear that in mind. You should define your record id fields to optimize data accessibility through allDocs().






          share|improve this answer





















          • Thanks for your reply. The query API is very slow on the first time running it. It is very fast after that. Is there a document say what happens on query API? Does it build index into views? Does it require a lot of memory if the database is big?
            – Zhao Yi
            Nov 23 '18 at 20:59






          • 1




            Views are reindexed at query time. So yeah, the first query might be slow but the others should be faster.
            – Alexis Côté
            Nov 26 '18 at 16:05











          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%2f53444344%2fhow-do-i-know-which-fields-are-indexed-in-pouchdb-if-i-use-query-api%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 seen the PouchDB Guide Bulk operations section Please use 'allDocs()'. Seriously.?




          Far too many developers overlook this valuable API, because they
          misunderstand it. When a developer says "my PouchDB app is slow!", it
          is usually because they are using the slow query() API when they
          should be using the fast allDocs() API.




          When designing your data structures it's very important to bear that in mind. You should define your record id fields to optimize data accessibility through allDocs().






          share|improve this answer





















          • Thanks for your reply. The query API is very slow on the first time running it. It is very fast after that. Is there a document say what happens on query API? Does it build index into views? Does it require a lot of memory if the database is big?
            – Zhao Yi
            Nov 23 '18 at 20:59






          • 1




            Views are reindexed at query time. So yeah, the first query might be slow but the others should be faster.
            – Alexis Côté
            Nov 26 '18 at 16:05
















          0














          Have you seen the PouchDB Guide Bulk operations section Please use 'allDocs()'. Seriously.?




          Far too many developers overlook this valuable API, because they
          misunderstand it. When a developer says "my PouchDB app is slow!", it
          is usually because they are using the slow query() API when they
          should be using the fast allDocs() API.




          When designing your data structures it's very important to bear that in mind. You should define your record id fields to optimize data accessibility through allDocs().






          share|improve this answer





















          • Thanks for your reply. The query API is very slow on the first time running it. It is very fast after that. Is there a document say what happens on query API? Does it build index into views? Does it require a lot of memory if the database is big?
            – Zhao Yi
            Nov 23 '18 at 20:59






          • 1




            Views are reindexed at query time. So yeah, the first query might be slow but the others should be faster.
            – Alexis Côté
            Nov 26 '18 at 16:05














          0












          0








          0






          Have you seen the PouchDB Guide Bulk operations section Please use 'allDocs()'. Seriously.?




          Far too many developers overlook this valuable API, because they
          misunderstand it. When a developer says "my PouchDB app is slow!", it
          is usually because they are using the slow query() API when they
          should be using the fast allDocs() API.




          When designing your data structures it's very important to bear that in mind. You should define your record id fields to optimize data accessibility through allDocs().






          share|improve this answer












          Have you seen the PouchDB Guide Bulk operations section Please use 'allDocs()'. Seriously.?




          Far too many developers overlook this valuable API, because they
          misunderstand it. When a developer says "my PouchDB app is slow!", it
          is usually because they are using the slow query() API when they
          should be using the fast allDocs() API.




          When designing your data structures it's very important to bear that in mind. You should define your record id fields to optimize data accessibility through allDocs().







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 23 '18 at 13:04









          Martin BramwellMartin Bramwell

          6991727




          6991727












          • Thanks for your reply. The query API is very slow on the first time running it. It is very fast after that. Is there a document say what happens on query API? Does it build index into views? Does it require a lot of memory if the database is big?
            – Zhao Yi
            Nov 23 '18 at 20:59






          • 1




            Views are reindexed at query time. So yeah, the first query might be slow but the others should be faster.
            – Alexis Côté
            Nov 26 '18 at 16:05


















          • Thanks for your reply. The query API is very slow on the first time running it. It is very fast after that. Is there a document say what happens on query API? Does it build index into views? Does it require a lot of memory if the database is big?
            – Zhao Yi
            Nov 23 '18 at 20:59






          • 1




            Views are reindexed at query time. So yeah, the first query might be slow but the others should be faster.
            – Alexis Côté
            Nov 26 '18 at 16:05
















          Thanks for your reply. The query API is very slow on the first time running it. It is very fast after that. Is there a document say what happens on query API? Does it build index into views? Does it require a lot of memory if the database is big?
          – Zhao Yi
          Nov 23 '18 at 20:59




          Thanks for your reply. The query API is very slow on the first time running it. It is very fast after that. Is there a document say what happens on query API? Does it build index into views? Does it require a lot of memory if the database is big?
          – Zhao Yi
          Nov 23 '18 at 20:59




          1




          1




          Views are reindexed at query time. So yeah, the first query might be slow but the others should be faster.
          – Alexis Côté
          Nov 26 '18 at 16:05




          Views are reindexed at query time. So yeah, the first query might be slow but the others should be faster.
          – Alexis Côté
          Nov 26 '18 at 16:05


















          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%2f53444344%2fhow-do-i-know-which-fields-are-indexed-in-pouchdb-if-i-use-query-api%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

          Berounka

          Sphinx de Gizeh

          Different font size/position of beamer's navigation symbols template's content depending on regular/plain...