Thread: What's Popular for CMS and RAD with PHP/PostgreSQL?

Using PHP and PostgreSQL only, what do you feel are the most popular
CMS and RAD tools out there?

I'm looking for free options.

On Jul 13, 2005, at 10:00 AM, Google Mike wrote:

> Using PHP and PostgreSQL only, what do you feel are the most popular
> CMS and RAD tools out there?

Drupal is a very nice CMS for PHP and PostgreSQL. I'm using it for
some consulting projects now and it has saved me a great deal of
time. Some of the useful features include:

- account management and access control framework
- form building, processing, and error reporting
- paging through lists of records
- full text search engine


John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL

John DeSoi wrote:

>> CMS and RAD tools out there?
>
> Using PHP and PostgreSQL only, what do you feel are the most popular
>
> Drupal is a very nice CMS for PHP and PostgreSQL. I'm using it for
> some consulting projects now and it has saved me a great deal of
> time. Some of the useful features include:

I too like drupal and use it with postgresql, but some of the Drupal
contrib module authors are still very mysql-centric and fond of writing
code that breaks when using postgresql (or doesn't support it at all).
Luckily, it's usually not too hard to patch yourself or find a patch.  A
lot of highly desirable functionality does not exist in the Drupal core
but instead is provided by these contributed modules.  Drupal still
recommends mysql and doesn't treat postgresql and mysql equally.  It
would be nice if Drupal would keep track of which modules had been
tested against postgresql, but they don't.  If there were a pool of
drupal/postgresql users willing to be testers, and module authors were
aware of this, that would help also.  I've been too busy to dive in and
suggest/coordinate this, though.

-Kevin Murphy

Hi Kevin,

On Jul 15, 2005, at 6:57 AM, Kevin Murphy wrote:

> I too like drupal and use it with postgresql, but some of the
> Drupal contrib module authors are still very mysql-centric and fond
> of writing code that breaks when using postgresql (or doesn't
> support it at all).  Luckily, it's usually not too hard to patch
> yourself or find a patch.  A lot of highly desirable functionality
> does not exist in the Drupal core but instead is provided by these
> contributed modules.  Drupal still recommends mysql and doesn't
> treat postgresql and mysql equally.  It would be nice if Drupal
> would keep track of which modules had been tested against
> postgresql, but they don't.  If there were a pool of drupal/
> postgresql users willing to be testers, and module authors were
> aware of this, that would help also.  I've been too busy to dive in
> and suggest/coordinate this, though.


Yes, I have noticed that MySQL gets better support. Hopefully more
PostgreSQL users will join in to improve the situation. But as you
say, it is generally very simple to update the table definitions for
contributed modules that don't have PostgreSQL support. And all of
the core modules have PostgreSQL definitions.


John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL