To be fair, that's the fault of the previous designer, not MySQL. You
don't blame Stanley when your contractor uses 2" plain nails when he
needed 3" galvanized. The tool isn't to blame just because someone used
it incorrectly.
MySQL works great for what it does: high speed at a cost of data
integrity. It's fine for discussion boards or anything non-critical
where having a database is a convenience instead of a necessity.
Nevermind that MySQL really doesn't have much place between PostgreSQL
and SQLite nowadays.
--
Brandon Aiken
CS/IT Systems Engineer
-----Original Message-----
From: Jorge Godoy [mailto:jgodoy@gmail.com]
Sent: Monday, August 28, 2006 3:36 PM
To: Brandon Aiken
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Precision of data types and functions
"Brandon Aiken" <BAiken@winemantech.com> writes:
> Oh, I agree. PostgreSQL is a much more well-behaved RDBMS than MySQL
> ever was. I'm more inclined to select PostgreSQL over MySQL, but I
may
> not be able to convince management that it's a better choice no matter
> how technically superior I can show it to be.
Just show them how much money they might loose with a simple bug as the
one
that was shown to you on the last post :-) Money speaks very loud for
any
manager...
--
Jorge Godoy <jgodoy@gmail.com>
