Hello, I'm not sure I understand this problem.
You're saying that in a RDBMS, you can query the database to help debug it. In Neo4j you also have query capabilities to help debug a database (e.g. Cypher, Gremlin), though our toolchain isn't as integrated as some of the SQL tools (e.g. neoclipse/webadmin don't yet have query support). Jim On 2 Aug 2011, at 21:39, sambodhi wrote: > Hi Niels > > Thanks for your reply! Adding meta info should certainly help but what I > exactly mean from complexity her is huge size of the graph with thousands > of nodes. For example, in RDBMS if there is some problem with a some user > information, I can fire a select query or I can use tools like sql developer > which allows me to debug where the problem is. But in case of graph database > am not sure if it would be feasible with neoeclipse to navigate through > thousands of nodes and debug. > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-how-to-scale-and-view-or-generate-reports-for-complex-graphs-tp3205010p3219983.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
