[development] Do not let postgresql hold back great patches

Earnest Berry III earnest.berry at gmail.com
Mon Nov 12 23:51:00 UTC 2007

I agree with the earlier statement. MySQL seems "smarter/easier" because
most devel in the Drupal work use it all the time. I've been on other
projects where pgSQL is the "smarter/easier" method. 

Multiple-DB support is just good practice for a project that is to be widely
adopted and touts itself as a "flexible" CMS. There's no fine print that
says "Flexible...only on Apache 2.2 running CentOS 5 with kernel X; further
MySQL 5.x and PHP 5.1x and only with the following php libs installed....".
We not doing data-warehousing, or complex SQL Data cubes using
mutli-dimensional series slices...thus, in my very humble opinion, we SHOULD
be able to support multiple database with just good clean SQL code and
logic. We, as a community, should also be able to handle the "situations"
that arise b/t databases types; such as this case-insensitivity issue. We
all have friends across the pond ( and by pond I mean a linux guy has a
windows-expert friend, a MySQL guy has a PostGres friend, etc. etc.), and
could be able to cross that pond for information to help form a solution.

Anyway, that's my 2 bits...well, 1.5 bits.

More information about the development mailing list