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: 3, Informative) by Thexalon on Thursday May 04 2017, @05:27PM (2 children)

    by Thexalon (636) on Thursday May 04 2017, @05:27PM (#504416)

    Keywords are one of the things you care *least* about. Proper names, and lower/camelCase make SQL readable.

    On the contrary, keywords are what I care about the most! I for one want to be able to tell immediately whether what I'm looking at starts with the word "delete", for instance, because that matters more than exactly what table(s) I'm going to be looking at. What you seem to be describing is the equivalent of a syntax highlighter that highlights everything that's not syntax, which makes not much sense.

    ALLCAPS keywords in SQL is part of every single style guide I've read. You see it everywhere because the other developers are following a standard that has tested by time and thousands of people and found to work reasonably well. Trying to argue "I'm right and everybody else is wrong" is not likely to be a winner though.

    --
    The only thing that stops a bad guy with a compiler is a good guy with a compiler.
    Starting Score:    1  point
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by Nerdfest on Thursday May 04 2017, @05:44PM

    by Nerdfest (80) on Thursday May 04 2017, @05:44PM (#504426)

    You don't have to agree with me. I can't force you to be right.

    More seriously, the keywords stand out better using indentation, without being distracting, I think.

  • (Score: 0) by Anonymous Coward on Friday May 05 2017, @08:08AM

    by Anonymous Coward on Friday May 05 2017, @08:08AM (#504727)

    Meanwhile, everyone else knows that allcaps is mostly unreadable. Heck, lawyers use it for the important clauses they really don't want you to read because if you do you would never sign anything.