Closed (works as designed)
Project:
Submenu Tree
Version:
5.x-0.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Mar 2008 at 11:24 UTC
Updated:
27 May 2008 at 11:48 UTC
Jump to comment: Most recent file
Comments
Comment #1
bengtan commentedHi,
Yes. PostgreSQL is unsupported in 5.x-0.4 and previous, because ...
I haven't had any reason to use Postgres,
I didn't go to the trouble of setting up a Postgres server, and
I'd rather the submenutree.module fail fatally and noisily for Postgres than put in code that hasn't been tested.
If you know PostgreSQL, you're very welcome to provide a patch. It's only just the table creation part of .install, like you say.
Else, if you're happy to test for me, I can work on it, but probably tomorrow at the earliest (it's nighttime now as I write this).
Comment #2
bengtan commentedHere, try this quick change. You may have to totally uninstall and reinstall the module.
Also, I'm coding PostgreSQL (and blind) for the first time, so it might take a couple of tries to get it right.
Comment #3
bengtan commentedComment #4
peterdd commentedI personally have no urgent need.
There is no (warning) statement that this module isn't compatible to Drupal 5 "sold features".
The download tells "Recommended for 5.x" but there is/was no PostgreSQL support.
Maybe I missed it or Drupal hasn't a automated test environment where people can see reports what modules work for different environments and what not. The reports could be a table like this:
This table is probably an oversimplifation, I know.
The table could contain links to the module test results. This could help developers to know about problems they can't easily test/reproduce themselves.
Comment #5
bengtan commentedI think you'll have to address this issue to the drupal.org infrastructure or drupal.org webmasters.
AFAIK, the download system marks submenutree.module as "recommended" only because it's an official release rather than a development snapshot. I'm not aware of any capability or functional requirements.
I certainly didn't mark it as recommended - drupal.org did that itself.
As a related issue, when this module gets ported to Drupal 6.x, it should support Postgres automatically, because that's done by the D6 database abstraction layer.
Comment #6
bengtan commentedClosed due to lack of further feedback.