Raj, The write-up on MySQL though a bit dated does raise well-known issues. I have always failed to get any impression that MySQL was designed for high-end, large enterprise-level mission-critical database management applications with potentially hundreds and thousands of simultaneous transactions. Though, I do hear that MySQL has been deployed at a few centres with prominent names. Essentials like transaction support, stored procedures and the like were not there in earlier versions and while some things are changing in the new versions. I would keep an open mind as to how and what MySQL develops into.
The point I will make is: What kind of an RDBMS does a small business need? They may have just about one server and a dozen or perhaps 20 workstations. They may have about one database with 5 to 10 tables with not more than 5,000 to 50,000 records. And much of the database could consist of static information - say bibliographies and listings.... or even if database content changes regularly the system is not "heavily" used as in a large-enterprise...you get the picture. Now why would such an organization go for an over-kill RDBMS like ORACLE for example, if MySQL can do the job? One can bring in Postgres and other database environments into the discussion, but the fact is one would like to use the tool most suited to the task at hand. Leo At 10:10 AM 4/28/2002, you wrote: >http://openacs.org/philosophy/why-not-mysql.html > >This paper attempts to discuss some reasons to use and not to use >MySQL. While it's pretty old, some of the reasons would still be >valid. Comments? ================================================ To subscribe, send email to [EMAIL PROTECTED] with subscribe in subject header To unsubscribe, send email to [EMAIL PROTECTED] with unsubscribe in subject header Archives are available at http://www.mail-archive.com/ilugd%40wpaa.org =================================================
