Re: Technical refresh->Why MySQL?
| From: | Zeev Suraski | Date: | Sat, 11 Aug 2001 12:12:28 +0000 |
| Subject: | Re: Technical refresh->Why MySQL? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-62934@lists.php.net to get a copy of this message | ||
Guys,
Let's not turn this into a database fight. If PostgreSQL wants to use the engine, by all means, they're welcome to do that. It just so happens that MySQL actually showed active interest in doing this, whereas PostgreSQL did not.
Zeev
At 13:05 11-08-01, Ron Chmara wrote:
On Friday, August 10, 2001, at 06:25 PM, Zeev Suraski wrote:-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/Yeah. I sound like Monty (which is not all that of a bad thing), but I do think that the MySQL integration will happen within the next 12 months.Questions: Why can't PHP get deeply involved with a different db engine, something that actually supports whatever-you-damn-well-please-joins, row locking, transactions, and internal functions? Why is PHP focused on simple flat file db's, when they've been out of date since the early 90's? This love affair with a fundamentally simplistic db engine has always mystified me. Why not something faster, with more features, like PostgreSQL? Is it a social issue? Licensing? Promotion? Install base? Documentation? Ease of adoption for folks notused to relational design? -Ronabop --2D426F70|759328624|00101101010000100110111101110000 ron@opus1.com, 520-326-6109, http://www.opus1.com/ron/ The opinions expressed in this email are not necessarily those of myself, my employers, or any of the other little voices in my head.