Stories
Slash Boxes
Comments

SoylentNews is people

posted by on Thursday May 04 2017, @11:47AM   Printer-friendly
from the fun-with-injections dept.

SQL and relational database management systems or RDBMS were invented simultaneously by Edgar F. Codd in the early 1970s. The simple fact that both arrived early in the life of computing, and that for 90% of the time they just work, means databases have become a 'solved problem' you no longer need to think about.

It's like how MailChimp has become synonymous with sending email newsletters. If you want to work with data you use RDBMS and SQL. In fact, there usually needs to be a good reason not to use them. Just like there needs to be a good reason not to use MailChimp for sending emails, or Stripe for taking card payments.

But people do use other other email automation software and payment solutions, just like people use NoSQL databases. Yet even with other database technology available, albeit less mature technology, SQL still reigns and reigns well.

So, finally, here are 8 reasons we still use SQL 43 years after it was first cooked up.

It's clickbait, I tell ya!


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Grishnakh on Thursday May 04 2017, @08:12PM

    by Grishnakh (2831) on Thursday May 04 2017, @08:12PM (#504509)

    Using upper-case SQL keywords isn't going to make anything break; it's purely cosmetic. It's even less consequential than the old tabs-vs-spaces argument, or camelCase vs. under_score, etc. And this has nothing to do with managers anyway, this is something purely down to developers and their habits. My argument is just that it's basically monkey-see-monkey-do; people see it done this way *so much* that they just go along with it, because they're probably not writing that much SQL anyway (just some queries that are embedded into other code), and they really don't care that much, and assume that it's done that way for some valid reason and they're not going to bother questioning it because they know that while technically any modern SQL database isn't case-sensitive with those keywords, that it's usually better to just go with the flow, just like they do with any multi-person programming project where you have to follow the common coding style guidelines instead of just doing your own thing.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2