You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into a really weird problem: at some point (it didn’t happen before), transactions in my production environment suddenly stopped committing properly and there were no error messages. It was like they were just hanging, which meant locks weren’t being released and other requests couldn’t be processed. But my testing environment (using MySQL 8.0) didn’t have this issue. Then I set up MySQL 8.1 in the testing environment and imported the relevant data from production, and strangely, everything worked fine in the testing environment. After that, I reinstalled MySQL 8.1 in production and migrated the data, and the problem went away.
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨
Your Question
version
Description
I ran into a really weird problem: at some point (it didn’t happen before), transactions in my production environment suddenly stopped committing properly and there were no error messages. It was like they were just hanging, which meant locks weren’t being released and other requests couldn’t be processed. But my testing environment (using MySQL 8.0) didn’t have this issue. Then I set up MySQL 8.1 in the testing environment and imported the relevant data from production, and strangely, everything worked fine in the testing environment. After that, I reinstalled MySQL 8.1 in production and migrated the data, and the problem went away.
Here is some of my code:
The document you expected this should be explained
Expected answer
Has anyone else run into something like this?
The text was updated successfully, but these errors were encountered: