Re: Why not to use MySQL (Score 1)

Basically, it's been said before and it will be said again, MySQL is a good read-only database. As soon as you start adding or modifying records, things change. The lack of transactions is a major issue for people handling a lot of changes. Beyond that, there are also just a large number of features MySQL simply sacrifices in the name of speed. Table-level locks are probably my biggest gripe. If you don't want to risk corruption, you've got to lock the table and as soon as you do that in MySQL, you essentially eliminate any concurrent access to that table. Oracle and many others support row-level locks. There are other issues too in terms of feature set. For example, the lack of stored-procedures, sub-selects, views, and so on can really limit the usefulness of the database under many circumstances.