Re: Postgress and MYSQL - Mailing list pgsql-general

From merlyn@stonehenge.com (Randal L. Schwartz)
Subject Re: Postgress and MYSQL
Date
Msg-id 86isjfok2v.fsf@blue.stonehenge.com
Whole thread Raw
In response to Re: Postgress and MYSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:

Tom> "Bob Powell" <Bob@hotchkiss.org> writes:
>> I find the recent articles in various trade publications a little
>> disturbing due to the lack of PostgrSQL mention.

Tom> You are seeing the effects of MySQL AB's large marketing budget;
Tom> they have the time and money to cause such articles to appear.
Tom> I'm not sure there is much we can do to counter this in the short run.
Tom> (I do wonder how quickly they are running through that $19 mil
Tom> investment though ...)

My new buzz-meme (pass it along)...

"You're still using MySQL... that's sooooo 90's!"

:-)

Seriously, the space occupied by MySQL has been encroached by SQLite
from the low end (if you just want SQL access to a data file,
including transactions) and PostgreSQL from the high end (when you
want a full-featured database).  I think they've completely overlapped
at this point (especially when I just discovered yesterday that you
can register Perl callbacks for user-defined functions and aggregates
in DBD::SQLite!), so MySQL really doesn't have much of a win at either
end.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgress and MYSQL
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Postgress and MYSQL