Quote from: jyap at Apr 22, 2009, 04:10 AM
I do not know if oracle 11g is similar to MySQL or is very different, and how (if at all possible) will MODx be work with oracle 11g?
It is quite different, and using MODx on Oracle would not be possible with any current version (alpha, beta, or otherwise) of MODx. That said, the xPDO project on which MODx 2.0 (a.k.a. Revolution) is being constructed is an extension to the PDO DBAL (DB Access Layer) in PHP 5.1+ that provides an abstraction layer for working with objects regardless of what PDO driver you want to use. It is not complete, and currently only provides an implementation for MySQL, but PostgreSQL and SQLite versions are in progress, and an Oracle version is certainly possible with some work invested.
Quote from: Everett at Apr 28, 2009, 07:30 PM
Yeah... it’s not easy. I have one client that probably will need to hook their Oracle wagon up to the MODx horse. The idea is that their Oracle db contains the "actual" data, whereas the MySQL database (MODx’s db) contains the data about how to display the data. This lands us in a place where MODx needs a lot of additional CRUD functionality to tie into their Oracle DB... it might be feasible, but obviously, we’re eying Revolution for this. Currently, the CRUD project I’m working on basically holds saved sql queries and it uses PHP’s modules to execute them against the respective database.
xPDO provides CRUD facilities abstracted from the DBAL. Why wouldn’t you just use PDO to connect to the Oracle DB? You can do this in 0.9.6 or 2.0.0-alpha.
However, keep in mind that means every request which is dependent on both the MODx MySQL database, and the Oracle content database would have to endure the overhead of making two separate database connections. In addition, you cannot perform SQL queries across platforms to JOIN tables and the like, so without some very clever design, you will be limited in your ability to optimize the site for performance or scalability.