I think the discussion boils down to something more fundamental -- and that there’s no point in porting new databases to modx until the xpdo layer that Jason is working on is finished (which shouldn’t be much longer btw).
In the meantime if you truly need support for another DB outside of mysql, you’re certainly welcome to hack that in and submit the patches back to the devs. I am sure they’d love to have them.
But in regards to mysql and Open Source licensing, I find that I do not agree with your position Xsss4hell, but that’s a personal/professional/philosophical decision on my part. It comes down to the fact that if you don’t like their licensing model, don’t use their product. Simple as that.
Please let’s try to steer away from flaming each other and get back to the topic at hand: modx and alternative database solutions.
-
MODX Staff
- 10,725 Posts
Thank you Victor, and now for some more specifics on how MODx can be ported to Firebird in the future, using xPDO...
I believe the Firebird driver for PHP’s PDO database abstraction layer is still experimental and needs some TLC before it is really usable. Search for "PHP PDO Firebird" for more information. Apparently, you can use the Interbase driver to connect to Firebird, but I’ll have to do some more research on that. Also, this will only work for PHP 5.1+ if you have the proper drivers configured in PHP (or if you have PHP 5.0 with the PDO extensions from PECL installed). Alternatively, you could also implement a PHP 4-compatible driver for Firebird as part of xPDO’s partial implementation of PDO for PHP 4/5.0. This is used when native PDO extensions are not available, and I have drivers for MySQL, SQLite, and PostgreSQL implemented (though SQLite and PostgreSQL are not tested).
But, for now, Victor is right, this will only be possible once the new MODx core is released and all dependencies on MySQL in the MODx manager are abstracted. As for progress, a preview of the new xPDO-powered core will be available shortly after 0.9.5 final arrives (very soon), xPDO is already available as a standalone library (it’s still a beta with very little documentation, but contact me for SVN checkout instructions if you are interested in seeing it, or patiently wait for me to release a downloadable package once a couple of recently identified bugs are squashed), and a total overhaul of the manager for the new core is in planning.
Also, note that xPDO and the new MODx core will not be released as a single implementation that supports all databases. Instead, ports optimized for the other database platforms will be released as demand/contributions dictate. xPDO helps make it super easy to port the code to each database platform with a minimal amount of effort. In all reality, there will probably be very little differences in the ports.