couchdb - PouchDB views going forward with development of pouch-find -
first, i'm huge fan of couch/pouchdb. i'm in bit confused project going forward. first, happy when discovered views, ability merge various related documents. understanding helped after reading this document.
now, i'm bit concerned state of pouchdb views going forward pouchdb website says query (which focused on map/reduce , views) going away in favour of pouchdb-find. find()
lot, seems great @ basic things secondary indexes , queries based on keys lt, gr, eq, etc operators. doesn't seem have in way of aggregate views.
so, time turn community guidance :p think putting aggregate views of related docs powerful , cornerstone of couchdb (besides awesome power of sync/replication of course).
is going built pouchdb-find? if need functionality, how should include , going forward?
pouchdb contributor here, can clear of confusion. :)
map/reduce not going anywhere. it's going optional in future. can still use api written.
pouchdb-find
(based on cloudant query language, aka couch 2.0 "mango" queries) designed replace map/reduce simpler queries. lot of newbie programmers confused map/reduce api, because it's complicated want.map/reduce's "join" feature not doing magical;
get()
request joined document. same thing in own code, , have same performance characteristics.
so in future have ability use either pouchdb-find
or map/reduce, or both of them. in fact, that's case, since pouchdb-find
available beta plugin. :)
Comments
Post a Comment