4 ms·
I personally stoped reading after this sentence : > And while SQL statements are fun, it’s easy to drop all tables while futzing with a key or corrupting an en
by Twisell 6y ago
I personally stoped reading after this sentence :
> And while SQL statements are fun, it’s easy to drop all tables while futzing with a key or corrupting an entire repository with a malformed query.
This seem to indicate that the writer don't real get a grasp of very basic modern SQL databases features such as permissions, constraints and transactions.
Without such understanding how can one form an accurate comparison of NoSQL benefits vs SQL. Or maybe worse the author has a good understanding but prefer to make bold and false statements to push his point.
- mosselman 6y agoIt isn’t even a permission thing. If you are just trying to query some data you don’t accidentally replace “select” with “delete”. The author is trying too hard to put sql in a bad light. Any syntax I have seen to query nosql databases looks clumsy to me as well. Sql I am familiar with, so I am probably biased, but they both have they pros and cons.
- 40four 6y agoTotally agree, I thought this was a big red flag. What an odd thing to say. Sure enough, the rest of the article it littered with similar strange, and inaccurate assertions. This is not a good article.
- buckminster 6y agoIt reads like SEO spam: a plausible collection of statements scraped from other articles and then cobbled together with no understanding. It's a shame that stackoverflow has sunk to this.
- 40four 6y agoIt really does. Just kind of rambles, throws around a lot of tech words. Meanwhile none of the points really made any sense. Never really read anything on their blog before, but this doesn’t make me want to.