Hi, Myskl,
Here's the deal.
When developing support for Mysqli (php's transactional mysql
interface, as opposed to the rather dated mysql interface) for
CK-ERP 0.31.1, the simplistic generic CK-ERP mysqli driver (for
all middleware) that I developed failed intermittently when
running against Moodle 2.2.2 . The (dirty) solution that I went
for was to force a (Moodle 2.2.2 + CK-ERP 0.31.1 that used MYSQL
database) environment to fall back to the traditional embedded
CK-ERP mysql driver, which worked perfectly.
With Moodle 2.7.9, the choice of database had changed from mysqli
or mysql (among others), to mysqli or mariadb. If you choose
mysqli in your Moodle installation, your database calls are likely
to go through (Moodle 2.7.9's mysqli database layer + CK-ERP mysql
driver). This database call combo may have suffered from the
intermittent error that I mentioned earlier.
I have also try the mariadb (which is supposed to be fully
compatible to mysql) route. After adding mariadb detection to the
Moodle/CK-ERP connector, the installation works fine. However,
the installation suffers from the performance issue detailed in,
https://groups.google.com/forum/#!topic/ck-erp-en/2SzmcJpL77A
The (default-storage-engine=myisam) solution does not work well,
ie installation is still very slow.
As such, my suggestion, at the moment, is,
a) use postgresql or sqlite instead.
b) use ATutor + CK-ERP instead.
c) use Moodle (some version between 2.2.2 and 2.7.9) + CK-ERP.
[However, some other hitherto unknown issue(s) may pop up.]
d) if you are just testing various features of CK-ERP, use
(other supported middleware + CK-ERP) instead.
Best Regards,
CK