On 27/02/2010 05:41, Svetoslav Nedkov wrote:
Well the collection data is separate from the artifact data and from a
user collection we extract the artifact ids and then go to query the
artifacts database issuing a single query for all the artifact ids. From
where the multiple keys.
You can have a look at:
https://source.fluidproject.org/svn/fluid/engage/fluid-engage-kettle/trunk/src/main/webapp/services/myCollection/js/myCollectionService.js
the fetchAndMapCollectedArtifacts function.
There might be a better solution though.
Regards,
Svetoslav
Thanks for the explanation Sveto - this looks like it is yet another
consequence of our fateful precedent in storing data of different types
in different databases. This needs to be corrected as soon as possible
after 0.3 is released. The correct approach for this application is the
one described in this blog posting:
http://www.cmlenz.net/archives/2007/10/couchdb-joins
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
