Randal L. Schwartz wrote:
"Wiggins" == Wiggins D'Anconia <[EMAIL PROTECTED]> writes:
Wiggins> But what are the reasons for choosing PostgreSQL over MySQL? What's a
Wiggins> "real" database? Without providing reasons this is just FUD. I will
Wiggins> agree that if you are looking for a package closer to a "real
Wiggins> database" you will need to look past MySQL 3.x to the 4.x series.
But if you don't want to wait the next five years for MySQL to catch
up to where PostgreSQL is now, you might as well install PostgreSQL.
Don't quote the old "MySQL is faster" FUD, because that's not valid.
For example, SourceForge picked Pg over My based on *performance* as
one of the key factors, and the choice is well documented (see
<http://www.phpbuilder.com/columns/tim20000705.php3?page=1&print_mode=1>).
In every category, Pg is technically superior to My. The only way
My now wins is inertia or bolt-on compatibility with legacy apps
and legacy brains.
Wiggins> Regardless the OP should analyze the DB chosen based on their own
Wiggins> needs. Having a discussion about what makes a good DB is probably OT
Wiggins> for this group, so suggesting that a choice already made is inadequate
Wiggins> is as much OT.
I didn't see anything that insisted on MySQL. I was just trying to steer
the OP toward a better choice to keep the knowledge entropy to a minimum,
and remove the chance for "one more legacy brain that will need rewiring".
If you are on Windows, MySQL is the better choice. Unless, of course,
you want to mess with cygwin. Ick. Although when PG goes native Windows,
I'll be using it. : )
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
