fix: backport compatibilita MySQL 8.4 per update 2.3 - #1908
Draft
sajotrei wants to merge 1 commit into
Draft
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
sajotrei
marked this pull request as draft
August 24, 2026 23:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problema
Su MySQL 8.4 l'aggiornamento storico
2.3si interrompe durante la creazione delle chiavi esterne versoin_interventi.idcon erroreSQLSTATE[HY000]: General error: 6125.La migrazione del ramo
v2.10crea un indice non univoco suin_interventi.id; MySQL 8.4 richiede invece una chiave unica o primaria per una colonna referenziata da una foreign key.Correzione
Backport del fix gia presente su
master(e7a3f0f, "fix: retrofix per compatibilita mysql8.4"):in_interventi.id;codiceunivoco;codice;Verifica
git diff --checke7a3f0f.Non modifica configurazioni MySQL globali e non richiede workaround lato server.