Why Should You Use MySQL?
jeremymorgan.com
Why Should You Use MySQL?
1–10 of 38 posts
Re: Why Should You Use MySQL?
#2MySQL is to Postgres today as mSQL was to MySQL in 1998; more popular yet technologically inferior. In another 15 years, we will be having the same arguments about PostgreSQL and the thing that comes to replace it, whatever that may be.
MySQL is in production and we have to live with it. The defences in the linked article are all valid. MySQL is a very sharp tool and can be used effectively. But its time has passed. Start your new projects on a more solid footing.
Re: Why Should You Use MySQL?
#31 reason to use MySQL rather than Postgres:
1) Your legacy shared hosting site might provide MySQL and not Postgres.
There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}.
Here is 1 reason to use Postgres: data integrity.
"00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One example among many.)
Re: Why Should You Use MySQL?
#4I was just going to submit this and found it was already submitted, thanks. Curious to see how others are going to tear my case apart on this one.
Re: Why Should You Use MySQL?
#5I was expecting a more compelling case.
Re: Why Should You Use MySQL?
#6I was expecting a more compelling case.
A lot of people use it. It is the Java of databases.
Ironically, Oracle also is connected to Java.
Re: Why Should You Use MySQL?
#7RDS as a scaling strategy is also a good reason.
Re: Why Should You Use MySQL?
#8I was just going to submit this and found it was already submitted, thanks. Curious to see how others are going to tear my case apart on this one.
not tearing you apart, just a small correction - it's spelt PostgreSQL (small "g") - http://www.postgresql.org/
Re: Why Should You Use MySQL?
#9Personally I prefer PostGreSQL over MySQL for a drop in replacement on Linux based systems. It’s far superior in many ways, and something you should consider if you’re able to. Personally if I were to start a new business or had a Linux based environment and was in the planning phase I would choose PostGreSQL from the start. But it’s not always the best option for most people.
What a crappy defense.
There is little I like about MySQL but here's a few reasons I still recommend people use it:
1. It's already part of something delivering value to your business. E.g. Nagios, MediaWiki or some other LAMP stack solution you've deployed. It's there. You're using it. Learn to live with it, and be sure to BACK IT UP!
2. You need to work with data someone gave you that came from a MySQL system. E.g. a Wikipedia dump. Someone else already lived the pain of collecting data into MySQL, now all you need to do is refine it.
3. You're publishing data for someone else to load into their MySQL system (e.g. a Pentaho warehouse).
Re: Why Should You Use MySQL?
#101 reason to use MySQL rather than Postgres: 1) Your legacy shared hosting site might provide MySQL and not Postgres. There are also 9 reasons to choose one of {Postgres, MySQL} over {Oracle, SQL Server}. Here is 1 reason to use Postgres: data integrity. "00/00/0000 00:00:00.0000" is not a real date, but MySQL will helpfully insert it into your table if you try to insert NULL into a non-null datetime field. (One examp…
One thing that bugs me is MySQL will truncate a value if the column can't hold it all and will only issue a warning (by default?). Although in most instances I've already done the foot work of checking a value's length, it would be nice to be able to throw an exception when it occurs. Of course that could be the choice of my framework and not MySQL's fault.