Re:SQL is 43 years old – Here’s why we still use it today
by mysterydip on Tuesday May 02, 2017 @08:06AM
(#14245664)
The SQLite site says it better than I could: https://sqlite.org/whentouse.html
Personally I use NoSQL options for the "replacement of ad-hoc disk files" they mention on that page. Like many of the comments here, anything more advanced than that and I'm using a relational database.
Re:SQL is 43 years old – Here’s why we still use it today
by scarface74 on Tuesday May 02, 2017 @08:46AM
(#14245891)
I fell in love with Mongo when I first started using it 6 months ago - the whole NoSql thing appealed to me. Then I fell in love with Sql Server 2016's JSON support - the best of both worlds.
Re:SQL is 43 years old – Here’s why we still use it today
by plet on Tuesday May 02, 2017 @01:48PM
(#14248702)
For me, NoSQL works great when the structure of the data is unclear but you have a fixed identifier that you can key off. SQL when the structure is known and juggling multi-table transactions is not a big PITA.
I'm not sure about the mongoDB nightmare, for me its done everything as the documentation claims it'll do.
just look at the nightmare MongoDB has created in most startups a year later.