E-mail
This page is intended to collect reported issues from MySQL 4.0 installs so we can figure out fixes at some point.
From Howard Johnson:
Wanted to provide an update on my test installation of the 1.0 beta - lost
some time due to the holiday. This was an attempt to install the 1.0 beta
rev1834 on a Mandrake Linux 10.1 OE box running PHP 4.3.8 and MySQL 4.0.20.
After resolving some of the errors generated by the contacts.sql script
related to explicitly creating indexes before creating foreign keys, use of
the 'bool' data type instead of 'boolean' and such, I was still getting a
syntax error 1064 at the point where the script is going to create the
crm_saved_search table. Since the script was running fine to that point and
the tables up to there were in fact created, I couldn't imagine what was
causing the error. After a lot of cutting/pasting sections of script and
running the snippets to see what errors they gave, I eventually found that
deleting the comment block immediately before the crm_saved_search code block
eliminated the error. I have no idea why it works, but I can only suspect
some sort of file corruption or bad character somewhere, that was removed
when I deleted the comment block. I hate these kinds of errors.
Now that the setup.php4.sh script would run correctly, I had a database and
could log in to drupal and try setting up crm. I had already modified php.ini
to increase memory to 32M and execution time to 60. Log in to drupal ok, go
to administer, click on modules and I received the error "Fatal Error: call
to undefined funciton overload()
in /modules/civicrm/packages/db/DataObject.php line 3705"
This was similar to what Katherine encountered but in a different place.
Noting her experience I uncommented the first instance (AROUND LINE 11) of
the define('DB_DATA_OBJECT_NO_OVERLOAD', TRUE) statement and tried again.
Now I got a different error "Parse Error: unexpected T_STRING in
dataobject.php line 126"
This seemed strange to me since the script ran all the way to near the end
(line 3705) before generating the earlier error, where now it was only
running to line 126. On a wild-assed guess I re-commented the define
statement and commented out the last few lines of the script that beings with
a comment about ' 4.3.2rc1 technically being broken and 4.3.3 may have a
problem too.' The code begins with
if(!defined('DB_DATA_OBJECT_NO_OVERLOAD'))
and goes for 11 lines or so.
From Gerhard Killes
CiviCRM is incompatible with MySQL 4.0 (not to speak of 3.x).
killes@ferdinand:~/csl$ grep -r GROUP_CONCAT *
modules/civicrm/CRM/Contact/BAO/Contact.php: $query ="SELECT GROUP_CONCAT(DISTINCT crm_contact.id)";
modules/civicrm/CRM/Contact/BAO/Contact.php: $select = "SELECT GROUP_CONCAT(DISTINCT crm_contact.id)";
GROUP_CONCAT is only available from 4.1.
