[Koha-devel] Database updates

[Paul Poulain]

Le 02/01/2013 15:15, Jared Camins-Esakov a écrit :
> 
> Also, I have a correction to Chris's response: we will not need two
> separate sets of DB changes because I will be copying every non-linear
> update into updatedatabase.pl <http://updatedatabase.pl>. That was the
> reason for the CheckVersion() routine.
> 
Just to be sure I understand well. You will *copy* things into
updatedatabase.pl when pushing to stable.
Thus, we will have the patch in both old and new mechanism ?
The koha 3.12 will use the new mechanism and 3.10.x will use the old one ?

How will Koha behave for people upgrading from 3.10.x to 3.12 (once it's
released, of course), where a db change will have been applied with the
old mechanism and will be re-applied with the new one ? (I think the new
mechanism will just issue an error message about, for example a
"duplicate entry in XXX" or "already existing column YYYY" or "cannot
find xxx" (because it has already been removed and cannot be removed again).
If I'm right, then we just will have to warn in the new mechanism
comment "if you see message xxx, it means this change had already been
applied, and you can force apply it safely"

For those who don't know how the new mechanism will work (internally) :
each DB change, if there's an error thrown will appear as "failing",
with the error message. The administrator can then "force apply" a DB
revision. In this case, Koha will just mark "OK, this DB change is done"

(happy new year again!)

-- 
Paul POULAIN - Associé-gérant
Tel : (33) 4 91 81 35 08
http://www.biblibre.com
Logiciels Libres pour les bibliothèques et les centres de documentation