Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • Hmm... so SQL according to your statement is ill suited for highly structured data, like a general ledger or an order entry system?? I don't think this statement is quite what you meant.... Commented Sep 19, 2011 at 5:16
  • Like I mentioned in the question, I read it somewhere that SQL is not useful for data that follows a particular structure or has some graphiness associated with it. Does it mean that the NoSQL databases are able to handle the case better?? Commented Sep 19, 2011 at 5:21
  • 6
    Um, SQL is all about structured data, tables and foreign keys look pretty structured to me. And a database that supports WITH RECURSIVE takes care of many of the "graphiness" (or "tree-iness") issues. Commented Sep 19, 2011 at 5:25
  • 1
    @the_drow: I did say many, not all. There are probably things that a relational database can do without breaking a sweat that neo4j can't. Right tool, right job, etc. Commented Sep 19, 2011 at 5:54
  • 1
    MongoDB is web scale: youtube.com/watch?v=b2F-DItXtZs Commented Sep 19, 2011 at 8:01