Re: [Neo4j] Most Efficient way to query in my use cases

2011-06-15 Thread Jim Webber
Absolutely! Funny how entities start falling about the woodwork when you think graphy. There's a "purchase" entity that links the specific pen, shopper, and shop too. You might even boil it down to line items if that makes sense in this domain. And don't get me going on where the pen was (ethic

Re: [Neo4j] Most Efficient way to query in my use cases

2011-06-15 Thread Craig Taverner
Another common thing to do in this case is create a node for the purchase action. This node would be related to the purchaser (user), item (pen) and shop, and would contain data appropriate to the purchase (date/time, price, etc). Then traverse from the shop or the pen to all purchase actions that

Re: [Neo4j] Most Efficient way to query in my use cases

2011-06-15 Thread Jim Webber
Hi Manav, I think there's a relationship missing here. Pen--SOLD_BY-->shop That way it's easy to find all the pens that a shop sold, and who them sold them to. In general modelling your domain expressively does not come at an increase cost with Neo4j (caveat: you can still create write hotspo

[Neo4j] Most Efficient way to query in my use cases

2011-06-15 Thread Manav Goel
Hello, I am using neo4j as database in my website. I am having problem in deciding best way to query the database. An user buys, lets say pen, from a shop. User and shop are the nodes and pen is also a node . Relationships are like User1->buysfrom->shop1 User1->uses->pen buysfrom and uses are re