For far too long now I have sat idly by as the NoSQL movement spread across our industry. One after another, these so-called “databases” with weird names have been attacking the sanctity of my beloved relational databases.

By the way, what is it with these names? Mongo, Couch, Raven, Cassandra? What is this, OccupyDataStores? Whatever happened to SQL Server, Oracle g, DB 2, even MySQL? Now, those are names you could set your watch to!

But I digress. The time has come to stand up to the scourge of NoSQL. Today, I am calling on developers everywhere to join a new movement dedicated to bringing back the golden era of relational databases: MoreSQL (check out the sweet logo below):

What We’re About

We at MoreSQL believe in the following axioms:

1. Universal Applicability: there is no such thing as a problem which cannot be solved with relational databases. It doesn’t matter what you’re storing or how you need to use it. Tabular structures (which may or may not be linked via foreign keys) are the only way to go. End of discussion.

2. Ends Justify Means: as corollary to axiom 1, we will do whatever it takes to make SQL work for us. Views, stored procedures, cross-database calls: you name it, we’ll do it. Oh and by the way, using ORMs does not mean that you’re trying to shove a round peg into a square hole. They are beautiful and enchanting, OK?

3. Scale, shmale: relational databases can scale well enough. I mean, Facebook is running on MySQL, for crying out loud! Are you better than Facebook and its 10 trillion active users? I didn’t think so.

What We Can Do

My fellow MoreSQLites, allow me to present some techniques to aid you in your noble quest.

“SQL Everywhere”

The most effective way to promote relational databases is to put them anywhere you can think of.

First of, if you’re starting a new app, you should be using SQL (no IFs, ANDs, or WHEREs about it). Now, if someone on your team starts talking about using document or graph databases, I recommend a three-pronged strategy of “ignore, mock, and scowl” (in that order).

Second, if you already have a running app, you may need to get creative. Ask yourself this simple question: “Am I really using a relational database everywhere I can? Am I? Really?“.

For example, some people frown on using relational databases for caching application objects. “You don’t need SQL for stuff like that, it is unnecessary overhead” they say. Well, that may all be well and good, but since when was a movement stopped by well reasoned arguments? Wouldn’t be much of a movement if we let that happen! Also, just remember the First Axiom and you’ll be fine.

“Discredit, Discredit, Discredit”

Another simple yet effective technique is casting as much doubt on NoSQL as you can. Oracle set the bar quite high in this area with their fantastic “Debunking the NoSQL Hype” article from May of this year. I just wish they kept up a copy of it on their website so that we could all learn from their wisdom.

Final Thought

This fight will not be easy, but it must be fought and it must be won. Just remember: they may take away our queries, but they will never take our freedom (to store things in tables). Fight on!

You may also like:

Did you love / hate / were unmoved by this post?
Then show your support / disgust / indifference by following me on Twitter!

This post got 121 comments so far. Care to add yours?

  1. CW says:

    I was at hadoop world last week: trust me Facebook doesn’t use the relational features of MySQL, and they’re moving away from it entirely.

  2. CG says:

    How ironically: Cassandra is Facebook’s child. You fighting against something you have no idea.

  3. Simon Munro says:

    You can use my ProSQL trump cards that I handed out at a conference a couple of years ago. They’re like race cards, but for SQL.

  4. Elad Kehat says:

    Nicely said! Had to read to the comments to verify my suspicion that the post is ironic though. Almost flagged you as stupid for “Universal Applicability” 🙂

    • Alex Tatiyants says:

      Thank you Elad, glad you enjoyed it!

    • How can this movement support data management at very high levels, consider Facebook(we are discussing and mentioning it frequently), as their customer base increase rapidly they will need to make the data available to all their customers readily available and also at any point correlated. Is this movement going support such demands?

    • You are right Alex this fight is not easy but it should be fought and we have to won. So I am in. Please tell me what I can do for the SQL. Lets give them an answer for there their bullshit. B)

    • With data increasing so rapidly it will be real challenge to manipulate so much information instantly. Am fully with SQL for a better solution to the rising problem. Keep going Alex.

    • Miller says:

      It was a great reading Alex. I am in for complete support of SQL. We are using MsSQL for around 11 years now and we don’t think it needs any major changes or improvements. As of my experience it can be used for any type of application and this is best part of SQL.

      @Dylan Moore I am too ready for participating to a dedicated Forum discuss issues related to SQL and please let me know if you want any help of mine.

    • Kevin says:

      Hey Alex! You are doing a very great work. I am working on SQL for 23 years and now I can’t work on any other technology. And top of that I love working actually playing with SQL. From now on I am with you in this battle. Thanks for writing this beautiful article and for this initiative.

    • Good initiative. I use MySQL most of the time and find it really easy to use and follow. since it has a user friendly environment it is easy to embed it also. Keep up the fight. I also join hands with you to support this fight.

    • I am a database professional and my work mainly governs around SQL.I can’t imagine myself functional without MS-SQL.There is no better programming language than SQL when one comes to do with tabular problems.But I think with time,one needs to be more pragmatic and thoughtful in opting the correct form for the correct applications.I have dealt very little with the new NoSQL databases till date and have found it wonderful treating non-tabular data.SQL and NoSQL has a great future and will keep upgrading every now and then.It becomes imperative for the new developers and database professionals to learn new developments and be with the flow.

    • I work in a software firm and handle my database using SQL from over a decade.My job would be non-functional without MS-SQL.I find SQL as one of the best programming language to deal with data written in complex tabular forms.I believe one should keep himself upgraded with time and new developments in technology.Also being up-to-date with latest software, one can refine his choice in selecting correct form for the correct applications.I have not used the new NoSQL databases a lot but have found it wonderful treating non-tabular data.SQL and NoSQL are doing great in database management in future.It is very much necessary for the new developers and database professionals not to stick to the old,traditional ways but to learn NOSQL alongwith SQL and do not lag back in this race.

  5. jaksprats says:

    I am a big fan of SQL, I have been embedding a RDBMS into redis for about 2 years now:, and I agree SQL w/ some work (e.g. NewSQL) can tackle most of the NOSQL use-cases efficiently, but there are areas (e.g. hadoop graphDB) where non-relational models are many OOM more efficient. But I fully support your MoreSQL movement and would like to add that responsible SQL (i.e. best practices [use indexes, no full table scans, etc…], correct RDBMS for problem set [ranging from VoltDB to Vertica], etc…) should be a cornerstone of the MoreSQL movement 🙂

  6. fjxx says:

    Alex, instead of sharding, partitioning etc and spending developers time on mutilating SQL databases and make them do what they don’t naturally, why not make use of NoSQL alternatives where it makes sense? The bigger the developer toolset the better. No need to keep using tools and techniques where they aren’t directly applicable and easier and better alternatives are available.

  7. Cross says:

    As a rule, no one can say “I have the answer for everything”, SQL is not bulletproof and sure it’s not for any kind of problem, I will support something like: “use SQL to solve tabular problems and NoSQL to support non-tabular problems”, it’s better than saying that you can solve any problem with SQL and try to fit an elephant into a speed race car.

    As an architects we should try to provide the best tool for the job, not to fit the jobs in a tool, no matter if it’s the best on their field (I know that Oracle, SQL Server and MySQL rulz on their world).

    • Alex Tatiyants says:

      I agree with you Cross and thanks for reading!

    • Joshua says:

      Have you seen an elephant in a speed race car?!

      I have, and it is equal parts majestic and terrifying.

      It’s amazing what we can do with SQL if we just think inside-the-box. 😉

  8. itoctopus says:

    I can’t think of any application that can’t run on MySQL. It’s been more than 10 years since we started using MySQL, and we never ever felt we needed something better.

  9. Mr.South says:

    Yes, i totally agree, we should fight back to put binaries where they belong. In a table!. #Occupy MediumBlobs

  10. […] È sempre divertente vedere come, a fronte di un movimento o di una tecnologia X, non appena questa prende un po’ piede, si formi il movimento not-X. Il termine SQL fu coniato nel 1970 da Codd e dopo una trentina anni, precisamente nel 1998, Carlo Strozzi ha usato per primo il termine NoSQL. Sotto questa definizione sono poi andati a finire tutta una serie di sistemi che hanno avuto un grande successo (mediatico e non) in questi ultimi anni: CouchDB, MongoDB, Redis. E ora, dopo più 10 anni di NoSQL, nasce il movimento not-not-x: MoreSQL. […]

    • Marcos Eliziario says:

      One thing that scares me lately is the sheer amount of people that lacks the basic cognitive abilities required to understand a joke or irony. Is it caused by information overload? too much conferences and screencasts are really that bad for neurons?

      • Alex Tatiyants says:

        thanks for the comment Marcos.

        I too am surprised by the number of people who don’t get the joke. My theory is that there is so little intentionally funny stuff written about technology, people just don’t expect it. My hope is to change that, eventually 🙂

    • Marcos Eliziario says:

      One thing that scares me lately is the sheer amount of people that lacks the basic cognitive abilities required to understand a joke or irony. Is it caused by information overload? too much conferences and screencasts are really that bad for neurons?

  11. Lionell Pack says:

    I’ve always found that chucking Oracle and big hardware at SQL can do a tremendous amount to mitigate its shortcomings. Half a million bucks worth of blade servers and a few hundred grand in license fees is peanuts when compared to the purity of sticking to your SQL guns.

  12. select * from awsome; says:

    Awesome, about time too.

  13. C8E says:

    See also UNSQL 🙂

  14. I’m sure it was just an oversight, but you didn’t mention the use of Excel as a reporting engine for SQL. Over the past 10 years in corporate America, I’ve found that no tool is better served for extracting tens of thousands of rows from a SQL database for quick study.

    Business Intelligence, Dashboards and filtered web reports just don’t express data clearly enough.

    INSERT INTO MoreSQL.Supporters
    (FirstName, LastName)
    ('Wayne', 'Arthurton');

  15. hrbg says:


    My name is Robert’); DROP TABLE students;– my mom calls me Bobby Tables, and I want to tell you that I want more SQL everywhere !!!

  16. Sasikala says:

    since most of the students stick onto SQL only. give me some ideas to take nosql databases to students.

  17. Ha! I laugh at you, Alex Tatiyants! We, the NoSQL movement, have used and mastered these strategies since day one, and we will annihilate you!

    We will never admit that Facebook front end runs on MySQL! We’ll never admit that Twitter runs on MySQL! And by God, we will not even mentioned that StackOverflow runs on the unmentionable SQLServer!

    Instead, we’ll tell you that relational databases don’t work at scale. Ha-ha!

    We are NoSQL, and we will crush you, Alex Tatiyants!

    • Alex Tatiyants says:

      Hi polaretto, the term “backtracked” would accurately describe most companies who release a product based on a technology which they previously dismissed as immature. However, this being Oracle, I would change “backtracked” to “invented” (or at the very least “perfected”).

  18. Matt Freeman says:

    Proponents of NoSQL databases will be the first to tell you to use whats best for the task at hand, we are pragmatic people who in most scenarios use a mix of NoSQL and SQL in our toolset. Be it couchdb, redis, or good old mySQL or postgresql etc.. Tabular structures (which may or may not be linked via foreign keys) are the only way to go. End of discussion. Saying shit like that means youre only going to attract numpties. This isnt a war that you need to fight..

  19. Jim says:

    Im still pissed that people are carrying on about this MySQL. Whats wrong with Clipper 87?

    • Alex Tatiyants says:

      So true, so true. Once were done with SQL, lets be sure to bring back Clipper and maybe Lotus notes (the original vintage of course).

  20. Will says:

    I think youre more true than you realise; naturally, I had to blog about it 🙂

    • Alex Tatiyants says:

      Thanks for reading Will and im glad I was able to inspire a post (first and probably last time thatll ever happen).

  21. Mike says:

    Brilliant movement…

    I do however think that the OS layer can also benefit from this movement. If we write a kernel that can *only* do a single select from a named table to pull out the next bit of the boot loader as a BLOB and then strap from there I think well be getting somewhere. We may however need to modify UEFI. As far as I know it doesnt use RDBMSs anywhere. I dont know what they were thinking.

    • Alex Tatiyants says:

      Excellent point Mike, I never even considered the OS. Its thinking like this that will propel the MoreSQL movement forward, towards eventual world domination!

  22. Jason says:

    Im onboard! The logo itself was enough to sway me. I design dating sites so relational databases just make sense.

    • Alex Tatiyants says:

      Welcome aboard Jason! If I said it once, I said it a hundred times: logos make all the difference as far as movements credibility is concerned. Just look at HTML 5.

  23. ashu says:

    is it sarcasm ?

    • Alex Tatiyants says:

      Well, that depends on what you consider sarcasm. I mean, I didnt mean a word of it when I wrote it, so I suppose some might consider that sarcastic. Or not. Anyway, thanks for reading!

  24. Great initiative!

    Now that were a movement, people cant just ignore us anymore, dammit!

    Seriously – I love RDBMS-es, and I agree that for *storing* data, a normalized schema consisting of tables related through foreign keys is almost always the right choice.

    However, there is no reason at all that the language we use to manipulate the RDBMS should limit itself to that as well. In fact, if SQL would have better support for unnormalized, sub 1NF structures, it would application development much more convenient, and I think a good case can be made that data access can be done in much more efficient patterns.

    (To be clear, Im talking about a way for SQL to deliver and receive nested data structures, and a means to transform those structures to 1NF (or higher) tabular structures. Im not suggesting at all that RDBMS should *store* such structures.)

    I do think ORMs are a kludge (most of them anyway), they wouldnt be necessary if SQL would be more complete and support sub 1NF data.

  25. Brandon says:

    Great post!

    I’m a contract .Net developer (7 yrs) and enjoy coding from the Mid Tier up to the UI. I know SQL but when I found out about NHibernate and ORM Mappers I naturally moved to them so I can concentrate on my business logic, and let NHibernate worry about the SQL. But for complex queries nothing beats Stored Procs.

    These new NoSQL databases I’m really excited about. All I need to worry about now is the table name, and the id = key/values for the rows. Simple! Let the cloud worry about scaling and performance.

  26. Pedro says:

    Nice post, I am currently working with a great framework called SQL on Rails:

  27. […] is a cheeky idea Alex Tatiyants invented in NoSQL No More: Let’s double down with MoreSQL advocating that the cure for NoSQL is not less SQL, but even more SQL. Use SQL everywhere, for […]

  28. Thomas says:

    The only thing missing from this satire is a repeat of that joke we all saw retweeted ad-nauseum a couple months back: “These developers walked into a NOSQL bar, but then had to leave because they couldn’t find any tables.”

    Sadly though, you’ve pretty much nailed every “relational bigot” I’ve ever met while trying to explain benefits of an alternative technology. The conversation usually starts with me saying “…Oracle does some things very well, but it won’t solve the problem you’re describing. I can prove it. In fact, you’ll see orders of magnitude improvement and significant cost reduction over your existing infrastructure. Wanna see?” The surprisingly frequent reply was “Well, I don’t believe you. No I don’t want to see any proof. I think you’ve been drinking the cool-aid. And besides, we already have an Oracle site license – and our IT department has instructed us developers to use that to solve all our problems. Plus, upper management all have heard of Oracle, so it’s a much safer choice.” And the decision to stay safe, rather than solve the problem was invariably set in stone at that point.

    I’m glad to see the latest class of NOSQL technologies and developers now graduating up into these companies and organizations, so they can do more to change the mindset. It’ll take a few more years, but guaranteed, you’ll see more awareness and adoption of “the right tools for the right jobs”…

  29. […] early as last November, when, Alex Tatiyants published articles on NoSQL No. More: Lets Double down with MoreSQL , and issued the following call: Today, I call upon all developers to join MoreSQL, back to […]

  30. PJ says:

    This is a great blogsite Alex!…Always wondered where/how can one looking for an opportunity get into these new technological areas?

    • Alex Tatiyants says:

      Thanks PJ, glad you enjoyed the blog. As far as getting into new technology, there is a bunch of different ways to do that. You can try it out yourself, get together with others interested in the same technologies, or get a job at a place that encourages exploration. Good luck!

  31. Corey Mingo says:

    I couldn’t agree more Alex. The problem is that many developers have no formal training in relational database design. Some have no idea what normalization is. To them, a relational database is just a collection of tables anyways.

    Relational Database design is just a math problem. Arriving at a normalized design is just stating the solution in a preferred mathematical (normalized) form.

    Stating that relational databases can’t scale to your velocity or volume is as absurd as saying “A circle cannot scale” or “Trigonometry cannot scale” It’s just math. Tuple relational calculus is a relational algebra. How does math not scale?

  32. Provence says:

    Thanks for this great post, very funny writing making it even more pleasant to read.

    Regarding SQL, I do think it is definitily the most well rounded solution around. I have been using it for a while and have to say that regarding the needs I have had, SQL has always been the best tool for me, moreover I do not think that our industry would benefit from a change toward the noSQL direction.

  33. Rondomat says:

    Hey Alex,

    did you know that the NoSQL movement is already taking its forces to start a new promising “NoMoreSQL” Movement to strike you back where you come from? 🙂

    Anyway, I had a great laugh while reading your article.

  34. Nerd in a Can says:

    If you think NoSQL is any kind of answer for a moderately complex application, you should be fired. Really. This betrays a fundamental flaw in your understanding of application design.

    If you think an object database is useful, then it’s clear you don’t know how to build anything that actually IS useful. I assure you, a fancy version of a key value store is not needed. ANy language with named properties on objects can do it with 20 minutes of massaging.

    WHat IS needed is the ability to manipulate and aggregate statistics regarding relationships between various types of structured data….. without endless fucking looping to do so! But I don’t expect you to even be able to read that sentence let alone understand the need for it.

    • Alex Tatiyants says:

      Thanks for your thoughtful comment Nerd in a Can. It’s good to know that my writing can inspire such unadulterated passion from otherwise well-balanced and respectful individuals. Just to verify, you can both read and understand that last sentence, right?

  35. Otoni says:

    I am Brazilian, I’m 51 years old and systems analyst and developer Paschal and java for over 25 years, some say I’m old for my job, and unfortunately hear it boys and girls in the newly formed colleges and who know all technologies and even those still on the drawing board, these are the same boys and girls who can not distinguish what is and what a joke is a serious matter. sorry for my english and the readers of your blog. a hug

  36. Thiago says:

    Hi there,

    I’m also Brazilian and I first read the article in a technology portal from Brazil, for a moment I thought it was “legit” and then I came here to check the original text and I saw the tag. Whoever translated this text wasn’t aware of the joke and posted it as if it was a serious call to arms against NoSql (btw, you have some sort of profile in that site as a collaborator which is a little odd). There’s a mini flame war going on about this and people still haven’t realized it was supposed to be a funny (most likely the person who translated the text is not in the technology field).
    My favorite quote was “Tabular structures (which may or may not be linked via foreign keys) are the only way to go. End of discussion” especially the “end of discussion” 😛

    Anyway, good job at making me laugh 🙂

    • Alex Tatiyants says:

      Hi Thiago, thank you very much for reading and commenting on my post. My geek humor posts are frequently misinterpreted as serious articles, especially when read by non-English speaking audiences. I guess I’m going to have to clear up the misunderstanding on iMasters.

  37. Nuno Carvalho says:

    There is no war between SQL, or NoSQL, or NOSQL, or NewSQL, or whatever.
    People use what they need to solve their problems. And when you need scaling, you will need to find alternatives to an RDBMS. And it’s not true that Facebook is using MySQL out of the box. They are using MySQL only for a particular part of the system, and with a very particular configuration, that hardly resembles SQL.

    Take a llok at this post to learn about twitter:

  38. Sarah Gant says:

    Hi Alex! I am a mainframe developer and i use DB2 for applications i develop. SQL is a very essential for me as well. You are doing a great job and i want to join your movement for relational databases.

  39. The issue of structured database management is not clear to me in discussing MySQL. If Facebook is not so efficient in their application of MySQL how can they manage so many viewers 24×7.

  40. Moses says:


    I don’t understand why people have started to talk about NoSQL. The good old SQL RDBMSes are there for more than fourty years now, shining (sucking) our brains and applications, and we never complained about what non-sense is going on(, until recently). But now when SQL RDBMS have become mature enough to enlighten (goof) us more, we say that we should look for NoSQL. This is not fair. The good old tables are for everything. And one should be keep quiet if scalability is required. What is scalability, by the way? There is no such thing. We didn’t have it in 64KB RAM calculator grade (CPU power) PCs of 70s. And as Bill Gates said, you don’t need RAM more than 64KB.

    All you need is about 20 to 50 tables to model anything in the world. The referential integrity and normalization is there to help you. And you can store all the record of your shop in an RDBMS (how many items will you sell in a year? how many customers you can have?). Is there anything you can’t store in DBase 3+ or Foxpro? Or if you like many advanced features use MS Access!! If you want concurrent access to the DB, make a line please. Civilized nations use queues and lines to wait for their turn.

    So do you remember today’s lecture? all you need is a SQL RDBMS table.

    (To add flavor to the blog post, you can freely add my comments to the original post with your embellishment)

  41. Abigail says:

    SQL is too valuable operative to completely deny its use, does everyone has to name the holy cows too add mileage? Facebook has some remarkable ways to control such a huge crowd flow at any point of time. If SQL can do that I do not see any reason to follow NOSQL.

  42. Evelyn Basse says:

    I want to say only a single thing, In Wayne’s style…

    INSERT INTO MoreSQL.Supporters
    (FirstName, LastName)
    (‘Evelyn’, ‘Basse’);

  43. powell liam says:

    HaHaHa well said Wayne and Evelyn. I am also with you too and in your style…

    INSERT INTO MoreSQL.Supporters
    (FirstName, LastName)
    (‘Evelyn’, ‘Basse’);


    BTW I am big fan of MoreSQL and Alex good initiative, well done and best of luck. 🙂

  44. Clark says:

    Thanks Alex for posting this useful article. I am working as a DBA

    from last 2 years and knowing something new aboout SQL is really food

    for me. I like your post and want to join your group.

  45. Jayla Cooper says:

    Some jokes are eternal, your’s seems one. IS the movement moving? Keep moving.

    • Alex Tatiyants says:

      Hi Jayla,

      Yes, I do think that the movement is moving. I’m just not sure where it’s heading.

  46. Glad about the insightful movement. Recently joined as DBA anything pertaining to SQL interests me. I would like to join your movement. Although not an experienced hand with SQL, even a peck of information is great for an amateur.

  47. Hi Alex!
    Its worth reading this article. I am in complete support of SQL and want to be on the board. I am using SQL for
    last 9 years and will definitely do anything for my beloved SQL. 😉

    With Love,

  48. Jayla Powell says:

    An eventful year nearly completing Alex and I found the interest is still growing with more comments and chance encounters like me, good to make some change, can’t always control their destination, be on the flow and yes, SQL may consider praising this blog for raising some pertinent debates also.

  49. Dylan Moore says:

    Thank you Alex for starting this. Hope this initiative will lead us to some fruitful destination. I am working with SQL and think we can gain some respect if this can really be a movement. Plan any dedicated forum to discuss our issues. would love to participate.

  50. Davis says:

    @Dylan Moore – Right, we need a new forum for SQL, while there are lot of forums available but SQL is an Ocean, so there is no limit of issues on daily programming.
    Alex – Are you really planning for any forum? I would like to be first participant.

  51. Harry says:

    There is a case of NoSQL type databases but its not a solution I would use for complicated systems. Im part of a team where we have developed an advanced fuel analytic system which uses multiple node for data processing and storage.

    Our central server(s) uses MsSQL extensively due to sheer size of our data but on our small node computers which process small datasets or specific equations; we actually use Redis that temporary stores small amounts of data. This way, we don’t need to run large complicated resource-heavy databases on simple nodes.

    Ultimately, one has to look at the requirements of the project, solution and application. For large data intensive purposes, I believe one requires the aid of an advanced heavy duty systems such as MsSQL which does such a fantastic job. For small and less intensive systems, a non-SQL database may be more effective.

    All in all, one must understand the application, requirements and environment of the system. Once understanding the design of the system, one is able to make the right choice which may require with a non-SQL, MsSQL or even both types of databases.

    Thanks for reading this reply 🙂

  52. Victoria says:

    Its been appreciated for a long time that joins in database queries can be bad for performance. MySQL made its name with an unreliable storage engine called ISAM that didn’t enforce foreign key constraints. The only thing going for MySQL was speed and cost, which was a really good combination. Everybody started using it. I’ve already tattooed myself with MoreSQL and I’m distributing printed leaflets with the axioms in all major squares in town.

  53. Wood Alyssa says:

    I also a great fan of MySQL. I have been using it from the past 5 years, and find it very user friendly. I find this to be a very unique kind of fight. Keep up the fight!

  54. Jones Emma says:

    This fight is really unique. I am still learning MySQL hence not much familiar about its advantages. Sure it has an upper hand over the other programming languages. Once I master it, I will also support this fight.

  55. Lopez Mary says:

    Great fight. Keep it up. I am a user of MySQL and am totally addicted to it. I think its really cool to use. It is very user friendly and can be adapted to any environment.

  56. Madona jean says:

    I am a user of MySQL I find this program very well, I use it for 1year. I will subscribe to your rss feed …

  57. Keep up the fight! I use MySQL regularly and really find it very user friendly. I will also subscribe to your RSS feed. Keep going!

  58. SQL is a standard language for accessing databases.I am a learner of MySQL and am totally addicted to it. I think its really cool to use. It is very user friendly and can be adapted to any environment. Most of the SQL database programs also have their own proprietary extensions in addition to the SQL standard!Although SQL is an ANSI (American National Standards Institute) standard, there are different versions of the SQL language. However, to be compliant with the ANSI standard, they all support at least the major commands (such as SELECT, UPDATE, DELETE, INSERT, WHERE) in a similar manner. I will also subscribe to your RSS feed. keep it up.

  59. garegin says:

    eff yeah. Stupid hipsters only use technologies to look contrarian. What’s next, using frame relay in your coffeshop? The reason they tout Haskell or NoSQL is just to annoy people. They actually have little understand of the core reasons behind these paradigms.