| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | John DeSoi <desoi(at)pgedit(dot)com>, Mark Woodward <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [OT] MySQL is bad, but THIS bad? |
| Date: | 2006-05-18 17:10:37 |
| Message-ID: | 446CAA8D.2070700@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Jim C. Nasby wrote:
> 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.
Good Lord NO. I don't want a bunch of hacked up code *because* MySQL
does it this way, running on top of PostgreSQL.
I want to run PostgreSQL. If you want to run MySQL, run MySQL. If you
want to run Oracle, run Oracle.
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 solutions since 1997
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-05-18 17:16:06 | Re: [OT] MySQL is bad, but THIS bad? |
| Previous Message | John DeSoi | 2006-05-18 16:48:47 | Re: [OT] MySQL is bad, but THIS bad? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-05-18 17:16:06 | Re: [OT] MySQL is bad, but THIS bad? |
| Previous Message | Bruce Momjian | 2006-05-18 17:07:10 | Re: autovacuum "connections" are hidden |