Re: More grist for the PostgreSQL vs MySQL mill

>>>>> "John" == John Meyer <john(dot)l(dot)meyer(at)gmail(dot)com> writes:

John> I'd say fine, but why discuss the flaws of MySQL on a PostgreSQL list?
John> If you want to correct it, why not put that flaw on a MySQL list. And
John> yes, I agree, there is a difference between pointing out a legitimate
John> flaw and simply bashing for bashing's sake.

It's a valid discussion here (although better on -advocacy), because it helps
me have the right facts to present to clients about whether they should stay
with a legacy database in MySQL vs upgrading to a modern PostgreSQL.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn(at)stonehenge(dot)com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!