Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
0013390: container_id update script problems #6624
Reported by koelschejung on 11 Aug 2017 14:59
Version: 2017.08.2 Community Edition
I updated from Ubuntu-Repository, if i update the databases in setup, i get erros by update tinebase.
(Im log finde ich folgenden Eintrag: )
Andere User haben das gleiche Problem:
Nach dem ich die DB wieder zurückgespielt habe und das Paket Tinebase, als erstes aktualisiert habe, ging es bei mir durch. Bei anderen leider nicht.
This was referenced
Jun 10, 2018
Comment posted by WolfgangAndreas on 11 Aug 2017 21:14
i could fix this by manually updating the sql-tables.
It seems, that the data type of the first named column (in the above case: table=tine20_cal_resources, column=container_id) was not changed from int() to varchar(40).
Had to do the above steps for about 3-5 more tables, but didn't note the names.
Updating the data types should be checked during the upgrade-procedure.
Comment posted by pmehrer on 14 Aug 2017 09:34
the issue is that Tinebase must be updated first and actually in this case all (precisely: some affected) applications need to be updated in one run (!). We created a separate task to enforce this in the setup. (https://forge.tine20.org/view.php?id=13392)
To resolve this manually I would strongly advice not to alter the table structure manually! The right way to resolve this, is to set back the application version as listed below and then do an update for all application in one run.
So if you run partial updates (which will be not be possible anymore in the near future) please check the application versions (tine20_applications table). If they are higher than the versions listed here, set them back to the listed version:
then do a full update of all applications in one run!