fmayhar

Well, obviously, <i>we</i> care what the reasons are. And since none of us want to be in the position of chasing a constantly-changing codebase with our changes, we quite understandably prefer PostgreSQL support to be in the base itself. As far as I’m aware, the only person “whining” here is you, and you’re whining because the rest of us are asking for something that would make a lot of lives easier.

Personally, unless and until it supports PostgreSQL, I won’t be using WordPress. A lot of other people apparently feel the same way. Use your MySQL toy if you want, but some folks have real problems to solve. In the meantime, kindly take your nastiness elsewhere.

I’m glad to hear that things are going forward. For my needs, ADODB would be overkill; I just need a way to use my existing PostgreSQL installation. I suspect that most feel this way: the details don’t matter as long as it works. ??
(Responding partly to Mr. Anonymous up there.) Unfortunately I simply have neither the time or the interest to help out technically in this. I have a Real Job that demands my time, and any “free” time that I may have left over from that or my family goes to kernel work, which is what I <i>am</i> interested in. But I do value your work and by no means intend to imply that it was in any way a waste of time or useless. It’s just not suitable for my needs.
And I have been known to toss a few bucks toward worthy causes when I have it to toss.
Thanks for the responses. I’ll keep an eye on WordPress as it evolves…

Well, yeah, I took a look at your port. That’s what I don’t like about it: It’s a port. It means that as WordPress went forward I would be dependent on you (or, I suppose, myself, if I wanted to take the time, which I don’t) to re-port it. The idea is for WordPress to support PostgreSQL (and other DBs) directly. At the moment, though, I’m sticking with my current plan, which is to continue to use MT 2.661 until it becomes too painful to continue.
I do wish WordPress directly supported other DBs than MySQL. Unfortunately, it’s not the only one with this problem.

Well, put me down as yet another who has been avoiding WordPress because of the lack of PostgreSQL support. As someone else said, I’ve looked at it several times and really want to use it, but I already run several PostgreSQL databases and really want to avoid dealing with MySQL.
In fact, I just examined and tossed PostNuke for just that reason: It only supports MySQL (despite having Adodb embedded in it, it hardcodes MySQL support; when I saw that, I uninstalled it).
I really like the look of WordPress and very much want something to replace the heavily license-encumbered Moveable Type that I’m currently running. Too bad it doesn’t support more than MySQL. I would happily toss in $25, myself, if PostgreSQL support were to suddenly appear…