Author Topic: mysql error = future problems? (Read 2894 times)

inkwire · May 16, 2007, 11:59:32 am

When loading civicrm_generated.mysql, I received the following error:

Error

SQL query:

INSERT INTO `civicrm_acl` ( `id` , `domain_id` , `name` , `deny` , `entity_table` , `entity_id` , `operation` , `object_table` , `object_id` , `acl_table` , `acl_id` , `is_active` )
VALUES ( 1, 1, 'Edit All Contacts', 0, 'civicrm_acl_role', 1, 'Edit', 'civicrm_saved_search', 0, NULL , NULL , 1 ) ;

MySQL said: Documentation
#1216 - Cannot add or update a child row: a foreign key constraint fails

Above that it states ' Table: civicrm_domain "Table 'civicrm_domain' was not locked with LOCK TABLES"'

I was able to then import civicrm_data.mysql and thought nothing further and the rest of the install went relatively smoothly. Now I'm wondering if I should have paid more heed to the error and whether a problem will crop up as a result. I searched a bit on the forums and noticed that some people had the same error post-install that was resolved by making sure the following line was in civicrm.settings.php (which I did have set correctly):

Code: [Select]

define('CIVICRM_DOMAIN_ID' , 1 );
I do think it would've been helpful having some sample data to start me off as this is a first install on a test site. I was able to edit my own (ie drupal admin) info no problem and add a new contact. Is there anything I should be on the lookout for?

Much thanks,

Arp

Donald Lobo · May 16, 2007, 02:58:23 pm

what version of mysql r u using?

civicrm_generated.mysql is turning forien key checks off and then loads the db and then turns it back on. (this is generated by mysqldump).

I suspect your version of mysql does not understand the FK check off command or something like that.

civicrm_data.mysql is a hand written sql file and does obey FK constraints and hence u did not see the error. If your version of mysql is quite old, i'd recommend u upgrade in the near future

lobo

inkwire · May 16, 2007, 03:27:41 pm

Thanks for the response - my mysql version is 4.1.11. I saw that 4.0.x was not recommended - is mine out of date as well?

Donald Lobo · May 16, 2007, 04:07:11 pm

4.1 is still supported

but 4.1 has quite a few versions and we cant afford to test and deploy on all of them. You'll have to figure out the mysql error and how to get around it for your version

Note that CiviCRM v1.8 is the last version to support php4 and mysql4. the v2.x series will only support php5+ and mysql5+

lobo

inkwire · May 16, 2007, 04:09:21 pm

Thanks - hopefully I'll be able to figure it out!

CiviCRM Community Forums (archive)

News:

Author Topic: mysql error = future problems? (Read 2894 times)

inkwire

mysql error = future problems?

Donald Lobo

Re: mysql error = future problems?

inkwire

Re: mysql error = future problems?

Donald Lobo

Re: mysql error = future problems?

inkwire

Re: mysql error = future problems?