Ask HN: if not SQL then what?
There are plenty of public complaints about SQL lately, and there were some hot discussions here on HN about SQL/NOSQL.<p>I have a toy project in Haskell, an in-memory DB implementing some limited subset of SQL and transaction support. I started doing this to first learn more about STM, then lightweight threading (forkIO). I implemented JDBC binding too, and can use it from Java.<p>Every time stumbling upon the SQL/NOSQL debate I feel myself a dinosaur: I work on SQL DB and there are some folks in the Valley who have a periodical meetup against SQL. The question is: if not SQL then what? What are the problems with SQL (I'm not addressing particular SQL implementation problems and standards compliance here, just the language implementing relational algebra per se)?<p>For example, document-oriented DBs look nice, but what's the fundamental advantage? Key-value stores look oversimplified to me. Any other approaches I missed?