Re[2]: [PHP-DB] Re: MySql or postgre?

From: Date: Wed, 29 Nov 2000 22:28:48 +0000
Subject: Re[2]: [PHP-DB] Re: MySql or postgre?
References: 1 2 3 4 5  Groups: php.db 
Request: Send a blank email to php-db+get-4851@lists.php.net to get a copy of this message
At 6:49 PM +0300 11/28/00, Alexey Borzov wrote:
    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.
BH> Not in the least. It means outside developers want to use the BH> software for purposes the original developers didn't have in mind. BH> Since it is open source, they can do that. The fact that outside BH> developers consider MySQL a good base for further development is BH> testament to the original developers competence. ::shrug:: Transactions are a vital part of RDBMS. If its developers fail to understand this (or fail to implement them) - then...
You're arguing both sides of the question. Here you claim that the MySQL developers fail to understand the importance of adding transaction support, they are incompetent. Previously you argued that because they added transaction support, they are incompetent just because they didn't do all the work themselves. In any case, I doubt that the developers have ever claimed that transactions are *not* important, just that in their view other things (like speed) are more important for the applications they needed. The addition of transaction support happened because they were able to build on the work of others. You characterize that as incompetence. I'd say it makes a lot of sense to use that approach, rather than reinventing the wheel. I take it you never use any software you didn't write yourself, because that would mean you weren't competent to write it? -- Paul DuBois, paul@snake.net

« previous php.db (#4851) next »