CiviCRM Community Forums (archive)

I was attempting to delete an e-mail address today from an individual and got the following error:

     Sorry. A non-recoverable error has occurred.

    Database Error Code: Cannot delete or update a parent row: a foreign key constraint fails (`45_tears_civicrm_1/civicrm_mailing_event_queue`, CONSTRAINT `FK_civicrm_mailing_event_queue_email_id` FOREIGN KEY (`email_id`) REFERENCES `civicrm_email` (`id`)), 1451

    Return to CiviCRM menu.

Error Details:

Array
(
    [callback] => Array
        (
           

• => CRM_Core_Error
[1] => handle
        )

   

=> -1
    [message] => DB Error: unknown error
    [mode] => 16
    [debug_info] => DELETE FROM civicrm_email  WHERE (  civicrm_email.id = 1027 )  [nativecode=1451 ** Cannot delete or update a parent row: a foreign key constraint fails (`45_tears_civicrm_1/civicrm_mailing_event_queue`, CONSTRAINT `FK_civicrm_mailing_event_queue_email_id` FOREIGN KEY (`email_id`) REFERENCES `civicrm_email` (`id`))]
    [type] => DB_Error
    [user_info] => DELETE FROM civicrm_email  WHERE (  civicrm_email.id = 1027 )  [nativecode=1451 ** Cannot delete or update a parent row: a foreign key constraint fails (`45_tears_civicrm_1/civicrm_mailing_event_queue`, CONSTRAINT `FK_civicrm_mailing_event_queue_email_id` FOREIGN KEY (`email_id`) REFERENCES `civicrm_email` (`id`))]
    [to_string] => [db_error: message="DB Error: unknown error" code=-1 mode=callback callback=CRM_Core_Error::handle prefix="" info="DELETE FROM civicrm_email  WHERE (  civicrm_email.id = 1027 )  [nativecode=1451 ** Cannot delete or update a parent row: a foreign key constraint fails (`45_tears_civicrm_1/civicrm_mailing_event_queue`, CONSTRAINT `FK_civicrm_mailing_event_queue_email_id` FOREIGN KEY (`email_id`) REFERENCES `civicrm_email` (`id`))]"]
)


This is most likely an issue with CiviCRM. Can you please file an issue and we'll fix it in trunk and/or 1.8 depending on the complexity of the fix

lobo

not sure when it got resolved, but i'm pretty sure this is resolved in 2.0 since we use mysql to go ahead and do the cascaded deletions

verifying this would be a good thing to do

lobo