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
Maybe as a workaround we could delete all expired sessions from the table first? This should minimise the risk.
Overall the risk of this happening is quite low because session Ids are usually much shorter unless maybe customised with https://www.php.net/manual/en/session.configuration.php#ini.session.sid-length and the chance of two similar IDs for the first 190 char is quite low. It's actually so low there must have been some other issue there.
Actually better workaround be to update each SessionID... since we now hash the sessionID, we could iterate over each session and update the ID in the table maybe before running this update. The hash would be for sure less than 190 character and maybe it keeps their session alive as a bonus point?
see https://forum.matomo.org/t/error-upgrading-db-while-upgrading-to-4-0-0-b1/39478
The text was updated successfully, but these errors were encountered: