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 ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
