Re: Re: MySql or postgre?
| From: | Paul DuBois | Date: | Wed, 29 Nov 2000 22:17:03 +0000 |
| Subject: | Re: Re: MySql or postgre? | ||
| References: | 1 2 3 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-4850@lists.php.net to get a copy of this message | ||
At 12:23 PM +0300 11/28/00, Alexey Borzov wrote:
BH> MySQL is adding SQL functionality, so in the next few months the
BH> difference will become much smaller. Second parties are adding
BH> transactions and row level locking to the basic MySQL package,
BH> although currently the first is not yet gamma ware and the second is
BH> vapor ware. If these ever become reality, they will allow MySQL to
BH> function in an OLTP environment. Basically though, I think it's
BH> always going to be a niche database, although in a very large niche.
Well, a metaphor once again:
"Second parties adding transactions and row-level locking to the
RDBMS" is like "Second parties are adding 3D engine to Quake". It means one
thing: program's own developers are INCOMPETENT.
You're saying that because the MySQL developers don't do all of the work
themselves, that they're incompetent? That's an interesting claim.
Would you say that if, say, the Apache developers accept a third-party
hunk of code allowing Apache to do something that it currently doesn't
do, that they're incompetent?
Or how about third-party add-ons that work with Oracle? Does that mean
the Oracle developers are incompetent, because they didn't develop the
add-ons themselves?
--
Paul DuBois, paul@snake.net