3 Mar
2021
3 Mar
'21
10:25 a.m.
Le 03/03/2021 à 11:18, Joonas Kylmälä a écrit :
Not really sure it is more work than writing the current db upgrade procedures, maybe tiny bit, and a bit more if you want to be able to revert the DB upgrade as well (which is optional and I don't think we should even consider that for MVP implementation of this).
You at least need to modify the code so that it handles the intermediary state, don't you ? In the case of a column/table rename, you need to make sure both columns/tables stay in sync until the whole upgrade process is finished. -- Julian Maurice BibLibre