>so they can provide an easy migration from MySQL to Oracle when your app outgrows MySQL.
Based on personal experience, when databases hit that point, the logical next step is PostgreSQL if you're going to go through the pain of changing database engines. Or just do what $oldjob did and throw more and more resources at MySQL (256GB memory, anyone?).
I'm guessing there is a sizable slice of applications that would find PostgreSQL to be "good enough", and not need to buy Oracle subsequently.
Perhaps that's just paranoid, and Oracle is running MySQL out of the goodness of its corporate heart?