On Wednesday 15 June 2005 12:23, William Astle wrote: > And, finally, one last data point. Most sites don't come anywhere near > requiring the advanced features of any dbms. For the vast majority of > sites, any dbms will do the job. Mysql, postgres, sybase, etc., will all > work sufficiently for most sites. As a result, there's no compelling > technological reason (for *most* sites) to choose one over the other. > Thus, the preponderance of documentation and examples wins out.
I agree with William's point here. However, if I used MySQL to develop web applications (real apps, not just web sites), I'd probably be out of business. Simply because I would need to move most of the data management logic into presentation layer code. With a SQL standards compliant database that supports triggers and stored procedures, a great deal of data management can happen AT THE DATABASE where it belongs, and minimizes the amount of code that needs to be written, and promotes code re-use (so I don't have to write the same logic over and over...). Of course, this is a very high level view. MySQL now has some support for stored procs, and a good deal of the above argument depends on the complexity of the application, and how the app is architected... Not to mention the discussion is mostly academic - as William hinted at. My thoughts. Shawn _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
