When to choose Oracle over MySQL? [closed]

Question

I am a MySQL fan , however i want to know in which situations choosing Oracle over MySQL seems like the way to go .. like what would be the indicators which would make you say .. "I need Oracle for this project"

Update: As another fellow SOer pointed out, dont limit your answers to Oracle ... if you know of something better , please point that out too.

Answer 1

There are certain things that bother me with Mysql

I have to choose between enforcing contraints and transactions vs Fulltext Index (InnoDb vs MyISAM). This is really the problem number 1 for me (enforcing contraints and transactions is what makes dbs cool, but you need the fulltext search too...)

• It is not easy to "simulate" transactions in client code.
• If you don't enforce the constraints it is really easy to get inconsistent state of the db
• Without Fulltext Search you might get crazy with OR X LIKE %y%
• You have to create BEFORE UPDATE TRIGGER with RAISE ERROR for CHECK CONSTRAINT
• Mysql has bad performace when data becomes too large(I mean really large).
• Mysql creates poor execution plans
• Mysql has problems with more than 3 joins(let's better say multiple joins).

Oracle is the solution for all these problems, it is a full DBMS (transactions, CHECK contraints, a lot of options for views, fulltext search and much more.. ) but after all it is a matter of money.