Timeline for Issues with CiviCRM Tables During MySQL 8.0 Upgrade
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2023 at 21:57 | comment | added | Demerit |
You could try doing a grep grouping * on your entire site and see if any of the results don't have backticks and then look into those. It won't just be civi you'll also have to look at extensions and cms plugins and any other code. Another way is make a copy of your site on mysql 8 and click on most of the things in your daily workflow and see if they still work.
|
|
| Dec 5, 2023 at 20:56 | comment | added | Fatih ATEŞ | I'm currently using the MySQL Upgrade Checker via MySQLShell to identify any issues or recommendations that might arise during the upgrade process. Since we rely on this system daily, I'm concerned about potential errors post-upgrade that could disrupt our daily operations. I want to ensure a seamless upgrade without any errors that could potentially disrupt or compromise our daily workflow. | |
| Dec 5, 2023 at 19:54 | comment | added | Demerit |
If you go to your site, do you see any errors about grouping? If not, then you don't need to create an issue.
|
|
| Dec 5, 2023 at 18:39 | comment | added | Fatih ATEŞ | Right now, only the first issue remains. Regarding that, I created an RP as you suggested, but either what I wrote wasn't understood or I didn't grasp the answer. lab.civicrm.org/dev/core/-/issues/4825 | |
| Dec 5, 2023 at 18:37 | comment | added | Fatih ATEŞ | I removed the 'NO_AUTO_CREATE_USER' content from the 'sql_mode' option for issue 3. Then, I executed the query 'cv api System.flush triggers=1' from the CiviCRM API, and the problem was resolved. Thanks again, @Demerit. | |
| Nov 30, 2023 at 21:24 | comment | added | Fatih ATEŞ | Thank you so much for the valuable information you provided. With the API call, all updates, except for 11 tables, were completed within a few minutes. I had prepared myself to update this many tables individually. :) Thanks to you, I've been relieved from an incredible workload. I've also manually changed the 11 tables named snap_civicrm_v5_65_xxx using phpMyAdmin. Now, I'm moving on to the issue in the third stage. I'll keep you informed about the progress. | |
| Nov 30, 2023 at 15:43 | history | edited | Demerit | CC BY-SA 4.0 |
added 134 characters in body
|
| Nov 30, 2023 at 15:37 | comment | added | Demerit |
Ok I'll add a screenshot in a minute. See also docs.civicrm.org/dev/en/latest/api/#api-explorer. But for cv it is just a command line tool like grep or ls.
|
|
| Nov 30, 2023 at 15:32 | comment | added | Fatih ATEŞ | Could you provide a screenshot regarding how to use the CiviCRM API? I haven't used this API before, and having a visual reference would greatly help me understand its functionality. | |
| Nov 30, 2023 at 15:28 | history | edited | Demerit | CC BY-SA 4.0 |
added 387 characters in body
|
| Nov 30, 2023 at 15:21 | comment | added | Demerit | I'll try to update the answer a bit. You could use sql for the 2nd one, but it's safer and I think easier to use the api since it will run the correct sql for you. For the 3rd one, no you shouldn't use sql to alter the triggers because they are rebuilt automatically sometimes, e.g. on upgrade. So you'll first need to change your sql_mode in my.cnf or whereever it is set on your system. | |
| Nov 30, 2023 at 9:48 | comment | added | Fatih ATEŞ | Hello Demerit, I might not have a good grasp of English, which might be why I couldn't understand the 2nd and 3rd proposed solutions. Can't I solve these problems with the SQL query provided as a recommended solution? I would greatly appreciate it if you could provide a bit more explanation and clarification on this matter. | |
| Nov 30, 2023 at 1:01 | history | answered | Demerit | CC BY-SA 4.0 |