https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24262
Katrin Fischer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #11 from Katrin Fischer <[email protected]> --- (In reply to Martin Renvoize from comment #10) > OK.. I'm loving this work.. > > I just had a moment of inspiration though.. what about upgrades? > > Currently, we add to both an atomicupdate file (which gets put into > updatedatabase) and add nearly the same code into various .SQL files (now > becoming .yaml files) for install time. I'm now wondering if as a further > bug we could add a function into updatedatabase to walk through the tree of > yaml files to install translated missing default data at the end of any run > of updatedatabase and save ourselves from having to write the atomicupdate > and the yaml file for such DB changes? I think this might get a little too complicated. For example libraries might have removed sample data on purpose, changed or reconfigured it. It would be hard to differentiate. We will want to add a new notice on update, but should respect if a library deleted it etc. (hope I understood correctly). So I think having different mechanisms (triggered for new and for a specific update) would be better. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
