Depends on your use-case, what do you want to do with the data? If you just want to store the fact that the user was there a relationship is good enough. If the actual visit is a really important concept in your domain that also other things are linked to and which has its own identity then a node would be better.
On Wed, May 21, 2014 at 10:38 AM, Navrattan Yadav < navrattan.craterz...@gmail.com> wrote: > hi . i am using Neo4j 2.0.3 version. > i am working on a DB where we need to track user path based on some fixed > location. > > like which location is most visited. > > so what i am doing : > 1. Each user has unique node. > 2. Each location has unique node. > > when user traverse a location then which is better option : > 1. create a relation b/w location node and user node . relation name is : > username_time : so when ever a user traverse a location a new relation is > created. > or > 2. create a node new node which has user info and location info and time. > so when ever a user traverse a location a new node is created. > or > any better idea... Any suggestion would be highly appreciated. > > -- > 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, visit https://groups.google.com/d/optout. > -- 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, visit https://groups.google.com/d/optout.
