http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13068
--- Comment #46 from Paul Poulain <[email protected]> --- (In reply to M. de Rooy from comment #45) > (In reply to Katrin Fischer from comment #44) > > Hm. so how does the system figure out which is the new dev one it needs to > > run? By comparing all entries in updatedatabase to the directory's contents? > > Paul raised the same question earlier. It is answered in comment16. The code > builds a hash with all db revs. The time needed for that is limited, since > it does not really inspect the file itself. It just sees the reference to > the file. And what worried me also was the time dedicated to this test on each page. As the $version system does not change, this test, with a hash is run only when needed, which is A-OK (about the idea to put it in a configuration, I like the idea. About having some "forbidden to change, or with a specific warning syspref", i'm also A-OK, even if: * no-one I know ever made something as silly as changing the MARCflavour avec going live ;-) * the list of such syspref would probably result in forever lasting debates... ) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
