Timeline for Error executing 'Backfill civicrm_mailing_event_queue' in upgrade to 5.67.3
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2023 at 14:26 | comment | added | Demerit | It will be slow to add if there's lots of mailings but if you run it in the backend it shouldn't time out. If you do want to delete all mailings, you could just recreate the table completely to match a good db. | |
| Dec 21, 2023 at 14:13 | comment | added | Andy Clark | Looking at the foreign key constraints for civicrm_mailing_event_queue I see there are - none! This db was created in 2013 & has somehow missed out on db updates. One possible way to fix this is to delete all mailings, then add the FK constraints. Is that going to work? I'm thinking that simply adding the FK constraints with a lot of data might cause problems. | |
| Dec 21, 2023 at 8:29 | comment | added | Andy Clark | Almost - I had that problem so restored the database, ran the SQL to fix, and then ran the upgrade again last evening. The title of the first step that crashed was 'Update civicrm_mailing_event_queue to permit deleting records from civicrm_mailing_job' and this step is 'Backfill civicrm_mailing_event_queue to permit deleting records from civicrm_mailing_job' | |
| Dec 21, 2023 at 6:31 | comment | added | Demerit | Is this the same as civicrm.stackexchange.com/questions/46045/… ? | |
| Dec 20, 2023 at 23:50 | history | edited | Aidan♦ | CC BY-SA 4.0 |
added 14 characters in body
|
| Dec 20, 2023 at 21:31 | history | asked | Andy Clark | CC BY-SA 4.0 |