A friend who's some type of computer researcher explained he thinks SQL is really a factor of history. I made use of SQL for a long time and think the word what is completely relevant when confronted with database specific tasks.

My pal thinks the brand new frameworks (e.g.: django, etc) which are being released are earning things much more generic, making SQL an outdated database language. I'm wondering what others consider this.

SQL might be better, however it does what it really does much better than other things.

The truth that your friend didn't explain / realize / realize that Django uses SQL because of its underpinnings virtually invalidates the argument he tries to make.

ORM really are a fairly pricey abstraction layer when you're searching to cope with high end programs / sites. If you're doing complicated database queries (multi table unions / crossing points etc) and taking advantage of an ORM you probably well send the "raw sql" directly with the ORM towards the database.

You will find lots of people who'd like to consider that it's outdated. You will find a lot of reasons with this but essentially it comes down lower towards the relational-object mismatch. Lots of effort went into creating ORMs ("object relational mapping") that abstract away the database. In a nutshell, SQL has been treated like a problem that should be fixed.

Regrettably abstractions are leaking.

Databases and SQL is going to be around for a while in the future.

Shaun Attwood mentioned on Hanselminutes he believed that "SQL is much like set up language for that database" and I am inclined to agree. I additionally agree that SQL might be better however it will get the task done very well. And when you're employed within the Microsoft world you'll be able to do C# within the database directly, bypass sql altogether in support of LINQ to SQL or NHibernate, etc. then you've plenty of choices where you can move about writing direct sql. But in the finish during the day...after i require a really enhanced query...derive the actual SQL! ...kind of exactly the same reason why set up continues to be going swimming nowadays!

SQL is not going anywhere.

There can be other options (e.g., object databases, Large Table, graph databases), and those that can't stand SQL (e.g., Anti-SQL), but relaxation assumed that relational databases is going to be around for any very long time. Your bank is going to be using relational databases after we are all dead and gone.

Look at this: "Why would you use Saved Methods?". Disregard the title though: browse the content.

Your friend clarified their own question: SQL has outlasted all of the new frameworks because "data includes a lengthy lifespan": frameworks don't.