Hi, for example if we rename a DB column in Koha now we need to stop all the koha web server instances (or they stop responding because because koha checks that db revision is correct), do DB upgrade, start all Koha web server instances. With rolling upgrade we would first create another column with the same name and write & read data to both columns during the 1st step of upgrade, then in 2nd step when all web server nodes are using latest version we could upgrade again to newer version and just delete the old column and start using new one.
Ahaha, there is probably better explanation online if you search "rolling database schema upgrade" but hopefully the above clarfied my intention. Joonas On 02/03/2021 16:47, Magnus Enger wrote: > Den 02.03.2021 15:33, skrev Joonas Kylmälä: >> Hi, >> >> I opened a bug report for introducing rolling DB upgrade support for >> Koha. I would like to hear if you have anything to object to that or >> should we just go ahead and develop that? :) > > I must confess I am not 100% certain what you mean by rolling updates > here. Could you give some more details? > > Best regards, > Magnus > Libriotech > > _______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : https://www.koha-community.org/ > git : https://git.koha-community.org/ > bugs : https://bugs.koha-community.org/ -- Joonas Kylmälä Tietojärjestelmäasiantuntija Kansalliskirjasto Kirjastoverkkopalvelut PL 15 (Unioninkatu 36) 00014 Helsingin yliopisto _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
