On Wed, Mar 10, 2010 at 7:05 PM, <[email protected]> wrote: > All the more reason to go with postgreSQL. I never did see a reason for > selecting MySQL over Postgresql anyway. >
Well, there are reasons, though usually non-technical: politically and for brand recognition, MySQL can be an easier sell. I've had clients hire me for jobs just because I was a "MySQL Certified Developer" even though we all know what expert means ;) There are some applications, especially older ones, that were written specifically for MySQL rather than using a database driver model so that they can support MySQL "best" or only. Joomla and WordPress are two that I believe are still primarily MySQL, based on a quick Googling. MySQL also claims to have more alternatives for replication, although there's a lot of issues with that, depending on the particular data engine and topology you're trying to implement. I started out using MySQL, 'cause I thought that's what the 'M' in LAMP stood for. But I've since done a couple of jobs with PostgreSQL, and that seems to be a pretty good database, too. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
