A discussion covering the question of persistence in the next releases of MODX and current progress on relevant initiatives.
What success MODX has achieved over the past ten years is, in my opinion, entirely due to two core tenets that the community has always stood behind. Those ideals are modularity and extensibility.
It’s been over 10 years since Ryan, Raymond, and myself founded the MODX CMS project and a lot has changed in the world of both content management and web development in that time.
JetBrains—the makers of IntelliJ IDEA—have unsurprisingly created the only PHP development environment worth paying for a license of.
xPDO is a light-weight ORB (object-relational bridge) library that works on PHP 5, and takes advantage of the newly adopted standard for database persistence in PHP 5.1+, PDO.
There are a number of benefits to using xPDO instead of writing SQL directly against the database.
I've restarted work on SQLite support for xPDO, and things are looking good so far. This will be targeted at PHP 5.2's PDO driver for SQLite3, not the older sqlite2 PDO driver included with PHP 5.1.x that is no longer available via PECL. It may be easily adaptable however.
As a developer of an open-source software product that depends on MySQL, I'm very concerned with the recent upgrades at many hosts to a specific distribution of MySQL, version 5.0.51, that contains some critical bugs that affect many applications, not just MODx. And though workarounds can be found, it would require folks to patch installations, potentially reducing performance on complex queries, and generally inconveniencing multiple open source communities; it would sure help if MySQL could help stop the distribution of releases with such critical bugs.