[development] So why we do support postgresql?

Daniel F. Kudwien news at unleashedmind.com
Tue Jan 15 20:07:27 UTC 2008

> Still there are no testers. I want to reiterate my plea: make 
> postgresql support somewhat optional. If there are testers, 
> great, if not, go on with life. You can flame me, but this is 
> already the state of affairs just noone wants to admit. Just 
> see http://groups.drupal.org/node/6980 . Greg spoonfeeds you. 
> I know we will get testers for the rest of the week because 
> of this letter and then they will move away as it happened 
> uncounted times.

Basically, I have PostGreSQL available on Windows and Linux. So, basically,
I was able test patches.
However, as a regular Drupal community member and contributor (not yet so
much core), I don't know that *there are any* PostGreSQL-related patches
that could be tested. Indeed, Greg's overview is nice, but I didn't know
that it existed. Now I know, and I hope I can test some of them.

Middle-term proposal:
Categorization of issues has just been enabled for 'Newbie' and 'GHOP'
terms. Why don't we add another vocabulary for global issue categories like
'PostGreSQL', 'Performance', 'JavaScript', etc. ? That way, contributors who
like to focus or help out on a certain topic could easily *find* all related
issues (and probably subscribe to a feed).
If that categorization was also open for contrib modules, overall support
for postgres and the like may be increased.
Realization of this proposal would include that the category of an issue
could be altered in an issue follow-up, and not just at the time of issue
Furthermore, we should provide easy access to those categorized issues - the
'contributor links' block jumps into my mind immediately.


More information about the development mailing list