Could you annotate the field with a query instead? Like:
@Query(MATCH {self}-[p:PRIZES]-(prize:Prize) RETURN prize ORDER BY p.order
ASC )?
SetPrize prizes;
I note from the documentation that the older format is still used, so maybe
it should be:
@Query(START s=node({self}) MATCH
Did anyone make or get a Neo4j cartridge running on OpenShift?
--
You received this message because you are subscribed to the Google Groups
Neo4j group.
To unsubscribe from this group and stop receiving emails from it, send an email
to neo4j+unsubscr...@googlegroups.com.
For more options,
I think Hanneli looked into that? Did you get it working?
Cheers, Michael
On Mon, Sep 29, 2014 at 11:09 AM, del sanic delsa...@gmail.com wrote:
Did anyone make or get a Neo4j cartridge running on OpenShift?
--
You received this message because you are subscribed to the Google Groups
Neo4j
Hi
I have an algorithm implementation on of Neo4j using the native API. I
think of moving to Blueprints API in order to use other graph databases
too. I wonder how much is the overhead of the Blueprints API, because I
tested the algorithm and it need much more time to finish. Is there any
Which version are you using?
Have you upgraded version recently?
Are you comfortable sending your zipped up database (the whole folder) to
me, or similar, so that there's a higher chance the cause can be found?
On Sun, Sep 28, 2014 at 1:38 PM, Ronen Ness ronenn...@gmail.com wrote:
hi all,
The use case is this:
Our application is based around data harvested from Twitter; we have unique
nodes to represent tweet authors, we have different types of relationships
representing the different types of connection between two nodes, and those
relationships have several properties that