Postgres Pro
Downloads
Home   >   mailing lists

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

From Jim C. Nasby
Subject Re: [OT] MySQL is bad, but THIS bad?
Date
Msg-id 20060518162421.GK64371@pervasive.com
Whole thread Raw
In response to Re: [OT] MySQL is bad, but THIS bad?  (John DeSoi <desoi@pgedit.com>)
Responses Re: [OT] MySQL is bad, but THIS bad?  (Josh Berkus <josh@agliodbs.com>)
Re: [OT] MySQL is bad, but THIS bad?  (John DeSoi <desoi@pgedit.com>)
Re: [OT] MySQL is bad, but THIS bad?  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: [OT] MySQL is bad, but THIS bad?  ("Dawid Kuroczko" <qnex42@gmail.com>)
List pgsql-hackers
Tree view 
On Wed, May 17, 2006 at 09:35:34PM -0400, John DeSoi wrote:
> 
> On May 17, 2006, at 8:08 PM, Mark Woodward wrote:
> 
> >What is the best way to go about creating a "plug and play,"  
> >PostgreSQL
> >replacement for MySQL? I think the biggest problem getting PostgreSQL
> >accepted is that so much code is available for MySQL.
> 
> 
> http://pgfoundry.org/projects/mysqlcompat/

Even better would be coming up with a compatability mode, a la what
EnterpriseDB has done for Oracle.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-hackers by date:

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