Re: [OT] MySQL is bad, but THIS bad?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Lukas Smith <smith(at)pooteeweet(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [OT] MySQL is bad, but THIS bad?
Date: 2006-05-18 20:25:34
Message-ID: 446CD83E.9050901@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers


> I do agree that its probably not worth allocating core resources to
> this, but spouting outdated FUD is really making you two look foolish.

And which FUD would this be?

>
> You have to understand that MySQL evolves just like PostgreSQL does. So
> you better focus on advertising where PostgreSQL shines instead of
> poking fun at something you apparently do not follow.

Uhmmm, I am not even going to bother responding to this part. It is
obvious that *you* don't follow MySQL versus PostgreSQL.

No offense but the development models and thus evolution thereof are
completely different.

Sincerely,

Joshua D. Drake

>
> regards,
> Lukas
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

--

=== 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/

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2006-05-18 20:26:39 Re: [OT] MySQL is bad, but THIS bad?
Previous Message Chris Browne 2006-05-18 20:25:17 Re: [OT] MySQL is bad, but THIS bad?

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-05-18 20:26:39 Re: [OT] MySQL is bad, but THIS bad?
Previous Message Chris Browne 2006-05-18 20:25:17 Re: [OT] MySQL is bad, but THIS bad?