[aerogear-dev] aerogear-js CouchDB data-manager adapter
lukas.fryc at gmail.com
Mon May 26 07:55:06 EDT 2014
great job with the adapter!
since there are obviously many ways how to achieve "delete all docs",
I believe it's up to user to choose the way he wants the docs deleted
i.e. it could be up to Data Manager configuration whether data will be
deleted with or without a history loss (aka wipe out). wdyt?
It would be pretty overwhelming for a user to create a view per particular
use of the filter() method, since it can have pretty arbitrary form.
We are also able to create temporary views, but that requires you to
perform one additional POST request and it is costly.
Are we able to come up with a common view definition that would cover all
the filtering capabilities - i.e. generic aerogear-filter view?
Something that user would define once and all cases would be covered.
I have not practically played with CouchDB, but according the docs it could
be somehow possible.
Btw as I think about it, there might be lack of function for limiting what
data to transfer.
i.e. Filtering API allows you to select just particular docs, but it does
not help you to avoid what will be transferred.
All the Data Managers so far are local ones, CouchDB is a first one that
actually transfers data from the wire.
On Mon, May 26, 2014 at 8:40 AM, tolis emmanouilidis <tolisemm at gmail.com>wrote:
> I have started working on creating a CouchDB data-manager adapter which
> uses the CouchDB REST API. The open-create database, read and save
> operations are implemented  and tested both with encryption settings and
> without encryption settings. If you'd like to give it a try, make sure that
> you have enabled CORS on CouchDB side.
> The remaining functions that needs to be implemented are remove and
> filter. In addition, in order to keep consistent the data-manager API, we
> should provide a way to remove all the documents in a CouchDB
> a) Removing all documents in a CouchDB database
> I'm thinking of fetching all the docs, using _all_docs endpoint which
> returns _id and _rev (revision), mark them as _deleted and use the bulk
> insert/update API to delete them. Not sure if this is a proper solution
> since there might be a huge number of documents.
> Another option would be to delete the database-store. This seems to be the
> worst solution since the documents history will be permanently lost.
> Any ideas?
> b) Filtering
> AFAIK, in order to perform filtering in a CouchDB database, a design
> document and an appropriate view has to be created. My thought is that the
> AGJS adapter should not create the view, instead we should assume that the
> user has created the appopriate views and provide a setting in AGJS where
> the view endpoint URl can be set.
> Any ideas about filtering and the proper way to be implemented?
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the aerogear-dev