Hello Tobias, Yes, this change only affects new sogo/database when sogo creates the tables at init. If you already have a database, you will need to make this change manually. However, it is only needed if you're using openid and see error when writing data to the database, as access_token can be very long. If you don’t see any errors, no need to do anything.
Thank you for your PRs, I didn't have time to see your new one yet. I have current devs on SOGo 6 that needs my entire focus. Cheers, -- Quentin Hivert Lead Dev R&D [email protected] Alinto 19, quai Perrache FR-69002 Lyon https://www.alinto.com Linkedin FR -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Tobias Weiß Sent: vendredi 13 mars 2026 11:01 To: [email protected] Subject: [SOGo] Questions about Commit f8638a3 fix(db): increase some column size Hi, Thank you for the lastest 5.12.5 update. Overall, I am pretty happy! However, :-) ... I have a question about following commit: https://github.com/Alinto/sogo/commit/f8638a3f4edd3487901c119b079dea2a3746cd7c It alters DB column types and there is no migration for existing installations. Are these changes mandatory? Could you please provide some brackground about it and maybe even a migration script? What do you think about my attempt: https://github.com/Alinto/sogo/pull/376 Best, Tobias
