The hosting has to do with the marriage, since any beginner, without any prior preference or experience, will just use what is provided, and stick to it. Yes, LAMP exists, but that's hardly an argument. Hostings do not use LAMP. Also, I'm not sure why you would say there are no alternative DB's having such a package. See for example LAPP for PostgreSQL or LAFP for Firebird. Either way, a one-time procedure like installation being a few minutes faster is not a good reason to base your choice upon. It's not important for the beginning web developer (who has his software installed for him) nor for the hoster (who does not use LAMP but will build himself) nor for the advanced solutions (who will gladly invest some time and money in a properly configured database of choice).
I refer to the cheap hostings as the type of hosting a beginner will most likely buy. As opposed to having your own server (park), sysadmins and DBA's. In the latter case, you will most definitely choose any software package you like and need for you solution.
About the tools, you can argue. I lke MySQL's Workbench, but the standard interface of SQL Server worked like a breeze that one time I used it. PGAdmin is very good, other MySQL tools I never tried. Open source is a good way to help the possibility of good tools, but it does not ensure it is better than a closed-source money-thrown-at tool.
Powerfulness of the DB's is not just an opinion, plenty of benchmarks along with the documentation itself back it up.
I misinterpreted the GPL License of the community edition, and thought you could only use it non-commercially. My bad there. It is not the only DB with a free version, though, as I said previous post.
About the safety: I am inclined to let your experience count, but seriously, it is hard to draw conclusion from searching the NVDB. Closed-source software is not automatically unsafe, and open-source is not automatically safe.
Extensive support documentation is not unique for MySQL and no proof of ease of managing.
You do ignore important points I made though:
- MySQL is bad from user perspective. It misses important features when your needs go further than simple SELECTs and INSERTs. The engine is slower than most competitors.
- There are good, free, alternatives.
- No reason to use MySQL is not applicable for PostgreSQL, except availablity and popularity.
@h4ck3rpr0n3: Sounds reasonable, but you do not need to pay and MySQL does have problems. But if you're used to it now, well, don't fix what ain't broke. Just think about this thread if you ever want to do a FTS in a transaction
(APetrick please give a shout if you think we are hijacking your thread...