Hi Colin, I don't see a reason not to switch to pure CouchDB views for the object code query. Actually there is no need for full text search when it comes to a small fixed piece of data that is queried upon.
The only reason this view was implemented as a Lucene view is that the rest of the views I used were Lucene ones. Cheers, Svetoslav Colin Clark wrote:
Hey all, I have merged Sveto's wicked Object Code Entry screen into Engage trunk, and it's now wired up to the navigation bar and home screen. We're getting closer! At the moment, you'll notice all object codes are invalid. This is because I still need to implement the view in Couch DB for searching artifacts by code. Sveto, your database uses a Lucene view for searching object codes, but I'm thinking this can by achieved more simply with a standard Couch view. Yura has already created such a view, called "viewByObjectCode." Take a look at it in Futon: http://142.150.154.59:5984/_utils/document.html?mccord/_design/artifacts Any reason I shouldn't go ahead and modify Object Entry to use this view instead? Colin --- Colin Clark Technical Lead, Fluid Project http://fluidproject.org
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
