io/en/release-1.2/couchdb_tutorial.html]: How to set up a CouchDB data store (which allows for rich queries). Private data [https://hyperledger-fabric.readthedocs.io/en/release- 1.2/private_data_tutorial using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which

CouchDB State Database With Pagination: Clients can now page through result sets from chaincode queries, making it feasible to support large result sets with high performance. Chaincode for Developers: using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which

using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which date from almost 1000 years ago, and the Sumerians had stone ledgers [http://www.sciencephoto.com/media/686227/view/accounting- ledger-sumerian-cuneiform] 4000 years ago – but let’s start with a more up-to-date

using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which date from almost 1000 years ago, and the Sumerians had stone ledgers [http://www.sciencephoto.com/media/686227/view/accounting- ledger-sumerian-cuneiform] 4000 years ago – but let’s start with a more up-to-date

using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which date from almost 1000 years ago, and the Sumerians had stone ledgers [http://www.sciencephoto.com/media/686227/view/accounting- ledger-sumerian-cuneiform] 4000 years ago – but let’s start with a more up-to-date

using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which date from almost 1000 years ago, and the Sumerians had stone ledgers [http://www.sciencephoto.com/media/686227/view/accounting- ledger-sumerian-cuneiform] 4000 years ago – but let’s start with a more up-to-date

using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which date from almost 1000 years ago, and the Sumerians had stone ledgers [http://www.sciencephoto.com/media/686227/view/accounting- ledger-sumerian-cuneiform] 4000 years ago – but let’s start with a more up-to-date

using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which date from almost 1000 years ago, and the Sumerians had stone ledgers [http://www.sciencephoto.com/media/686227/view/accounting- ledger-sumerian-cuneiform] 4000 years ago – but let’s start with a more up-to-date

using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which date from almost 1000 years ago, and the Sumerians had stone ledgers [http://www.sciencephoto.com/media/686227/view/accounting- ledger-sumerian-cuneiform] 4000 years ago – but let’s start with a more up-to-date

using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only history queries — Query ledger history for a query result or a proposed ledger update. Application A receives the proposal response and, for queries, the process is now complete. For updates, A builds a transaction from all of the responses, which date from almost 1000 years ago, and the Sumerians had stone ledgers [http://www.sciencephoto.com/media/686227/view/accounting- ledger-sumerian-cuneiform] 4000 years ago – but let’s start with a more up-to-date