( :sigh: ) Well, I suppose that means most of us won't need to worry about updates to our MySQL installs for too much longer then.. maybe it's time to see what it'd take to make QSFP fully support using other free DBs.. or does it already? (I really never bothered to check since I already knew it fully supported using MySQL which I was using already anyway.)
I don't think the situation is quite that urgent… we should note that the features being moved are probably not used by all that many of us. While it isn't great that they're going in this direction in general, it does make some sense for them to be doing it, and it doesn't look like they're abandoning the open source version.
I may well have posted in haste, one of the other guys on the QSF project made it seem more urgent than it probably is. The trend is a bit disturbing though, even if they eventually put the code into the non-Enterprise source. Sun is a bit of a wild card in this area.
I/we do/did have plans to try and at least get PgSQL support working but that was slated for the 2.0 release series. Which is sadly not getting much attention because of the lack of participation by the other devs, and by the lack of my knowledge in the area of DB stuff. Really, I think a lot of the QSF engine needs a good kick in the head with a rewrite or something. The DB support and the skinning system especially.
20 Apr, 2008, quixadhal wrote in the 13th comment:
As ugly and evil as it is, have you considered using ODBC instead of the native API? I've been slooooowly trying to get some odbc code for Smaug working, and it's not a pretty thing. But, it does allow you to switch databases without having to change your code. For simple things like a forum or mud, you probably don't need to do too much that's DB specific anyways.
I don't really know much about ODBC or how to interact with it, so I doubt it'll happen at my hand. But if someone else were to come up with something I'd be more than willing to make sure the codebase for QSFP could support it.