Re: [OT] MySQL is bad, but THIS bad? - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: [OT] MySQL is bad, but THIS bad?
Date
Msg-id 446CBDBE.7070605@commandprompt.com
Whole thread Raw
In response to Re: [OT] MySQL is bad, but THIS bad?  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
> And MySQL is much closer to being a competitor now than they were in
> 4.1. And feature-wise they'll probably equal PostgreSQL in the next
> release. Will the features be anywhere near as robust or well thought
> out? No. But in a heck of a lot of companies that doesn't matter.

Your kidding right? Have you seen their "features"? Look at what their 
stored procedures are actually capable of.

The only thing that MySQL *might* pull off is a really good storage 
backend finally.

> Maybe a compatability layer isn't worth doing, but I certainly think
> it's very much worthwhile for the community to do everything possible to
> encourage migration from MySQL. We should be able to lay claim to most
> advanced and most popular OSS database.

Oh absolutely, I agree with you here but in order to do so in the most 
productive manner possible the community would have to be willing to be 
much more aggressive and much more antagnositic that I believe the 
community has the stomach for.

Sincerely,

Joshua D. Drake


-- 
   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240   Providing the most comprehensive  PostgreSQL
solutionssince 1997             http://www.commandprompt.com/
 




pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: [OT] MySQL is bad, but THIS bad?
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Compression and on-disk sorting