Future with MDB2

So the point of adding MDB2 to phxEventManger with 2.0 was an attempt to help support users with more varied database environments. But that's not what resulted. I've been a long-time supporter of PEAR, and I do still believe in the extension projects, but PEAR simply still does not have enough mainstream support for serious, public development to rely on it.

Less-technical users have messaged me many times for help getting PEAR and MDB2 to work, but what finally pushed me over the edge on this was my own attempts to get it running on a standard Dreamhost server this week. Dreamhost is about as mainstream as any host gets, and they do support PEAR and the ability to install additional packages. Dreamhost does not however support the latest version of PEAR, which is perpetually required to install current versions of packages. Sure I can perform a custom install of PEAR that ought to work, but the point was to make things EASIER for users regardless of their host or platform. And that's where the "under development and frequently updated" nature of PEAR packages fails.

So it's with a heavy heart that I'm announcing a change in the database backend for phxEventManager. MDB2 is not going away, but it will not be the default anymore. Functions for MySQL will be in place as the standard, and if someone does need MDB2 it'll be selectable through the config file. At this time I have no plans to write additional functions for anything but MySQL. These changes will be included in the next release of PEM, probably in a week or two. If you have any questions or comments about this change, please feel free to message me or post in the forums.

Posted by Kevin Hatch 2010-06-10

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks