[KLUG Members] MySQL adoption

[Adam Williams]

>> And a funny joke about the MySQL vs. PostGres wars:
>> http://jeremy.zawodny.com/blog/archives/001053.html
>> kind regards,
>> bill hollett
>Man, you had me thinking that was real until I forwarded the link to a 
>friend who passed me back this link:
>http://www.aboyandhiscomputer.com/churchsigngenerator/
>MySQL is great as long as you don't mind doing the work in the 
>application code rather than in the db. That is really what it comes 

Exactly,  of course, for many applications this is a perfectly acceptable 
approach.

It really only becomes problamatic when you have multiple applications 
(almost certainly developed by multiple entities/developers) that the 
logic-in-app simply does not work.  For things like intranets, etc... this 
usually isn't a problem.  An entire enterprise is another story.

>down to. For the small PHP apps I write MySQL is great. One day I might 
>get into a project large enough that I need the separation.

Then simply use a data abstraction layer, and continue to use MySQL so 
long as it meets your needs.  Several of these exist for PHP, besides just 
outright using ODBC; and the ODBC API is easy to use.  ODBC to either 
MySQL or PostgreSQL shows a sub-2% performance penalty;  easily worth the 
flexibility.

And the two-tiered Work-In-App-Talk-To-DB or 
App-Talk-To-DB-And-Do-Work-There isn't the only model.  The three tier
App-Talk-To-Logic/Logic-Talk-To-Db exists too, and many large applications 
use this - and in such as setup MySQL may continue to be perfectly 
suitable (only lacking real constraint support, stored procedures are less 
critical in a three tier model).