Hi everyone,
I was playing right now with the index api to do some fulltext search, and I
found something what I think is not good for the API.
The index API rely heavily on Strings, just like the following:
Index typeIndex = index.forNodes("places");
I do write the call to forNodes method a
URL:
http://www.ted.com/talks/nicholas_christakis_how_social_networks_predict_epidemics.html
Speaker is Nicholas Christakis (with James Fowler)
Idea predict adoption curve earlier by not watching random people but their
friends (who are by definition more connected)
Uses Friends Paradox: do you
Why not something as simple as:
for each(var role in roles) {
if(role == desiredRole)
return true;
}
return false;
From: user-boun...@lists.neo4j.org [user-boun...@lists.neo4j.org] On Behalf Of
Ville Mattila [vi...@mattila.fi]
Sent: Saturday,
Hi there,
I am getting pretty excited with the power of return evaluators in
traversing framework. However, since I am using the REST API, there
are certainly some restrictions.
I should build a return filter to return nodes with an incoming
relationship containing a certain value in one of its a
4 matches
Mail list logo