On Thu, Jan 13, 2011 at 10:00:28AM -0500, Yannick Warnier wrote: > Hi Peter, > > This is *GREAT* news. I think we should put that in the January > newsletter, if you don't mind (I know how to word that).
I'm fine with that. > Do you have a *procedure* that we might apply to CouchDB as well, for > example? The procedure I used was basically: 1) I added exception handling to the database class to get early errors instead of allowing it to silently continue. This is very important. 2) Load page, find cause of the exception and fix it. 3) if not done, goto 2 That's it :) All you really need is knowledge of MySQL's quirks with respect to more standardised databases and how to fix those. However, I think Couchdb will prove to be especially difficult because there are quite a few places where there are raw SQL queries being generated, which that makes it a lot more difficult to add an entirely different class of databases like Couchdb or other "NoSQL" DBs. I think it's important to focus first on getting other relational, SQL-based database systems supported. Perhaps SQLite or Firebird, and if people have access to them, MS SQL/Oracle. To keep this stuff working, it's important that the core developers run as diverse a setup as possible, so that no new MySQLisms creep back in (in newly written code). Also, an extensive testsuite would help catch errors, because I'm very sure that there still loads of problems I haven't fixed yet. It's hard to debug a complete application by just *using* it. Cheers, Peter Bex Solide ICT - http://www.solide-ict.nl _______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
