[support] Drupal: MySQL vs. PostgreSQL

[Ivan Sergio Borgonovo]

On Wed, 21 Jul 2010 10:35:48 -0500
"larry at garfieldtech.com" <larry at garfieldtech.com> wrote:

> The decision between MySQL and Postgres should be made primarily
> based on the existing skillset of your DB admin.  Drupal's queries

That's like saying all problems can be solved with a hammer because
you're a hammer master.
Drupal seems to be so successful because it is a development tool
with a really good CMS as an example application ;)

It can be wrapped around many other applications... and different
applications may have different requirements.
Different DB are more suited to different tasks.
Maybe you already have an application running on one DB and Drupal
is just the web UI.

The fact that the core CMS application doesn't need specific
characteristics of any DB doesn't mean it's not legit to develop
modules that actually make use of some characteristics that are
available to just some of them.

MySQL doesn't have full text search on InnoDB nor a mature GIS
data/index (if any??). I don't know how easy it is to develop C
extensions for MySQL (if possible???)...
So postgresql for example has dblink, hstore (a sort of EAV),
support for trigrams... and you can program your own if you need it
(I wrote a simple text similarity extension based on tsearch2
exactly for one of my Drupal projects and I hadn't used C for more
than 10 lines in years).

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it