[Koha-bugs] [Bug 7167] updatedatabase improvements

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167

M. de Rooy <m.de.rooy at rijksmuseum.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |m.de.rooy at rijksmuseum.nl

--- Comment #25 from M. de Rooy <m.de.rooy at rijksmuseum.nl> 2011-12-05 12:36:50 UTC ---
Comments from some (nut full) testing (no QA):

I see 3.07.01.xxx in the db revs.
But what is 3.07.01 ? When do you reach 3.07.02 now? After you installed all 50
dbrevs that are marked with 3.07.01?
Is that mechanism implemented in current code? When and how are we stepping to
3.07.02 ? 

About/version: 3.0600002 / 3.07.01.0002 / 3.07.01.0003
Listing them all is not helpful. 
I would say list the version number: 3.07.01 meaning something like: everything
below has been installed. And list the numbers of dbrevs installed for 3.07.02
and higher and the number pending. 
So this would be: 3.07.01 with 36 db revisions installed; 23 db revisions
pending.
I agree that this kind of change is cosmetic but should follow quickly. 

Question: Do you allow someone to install dbrev 3.07.03.xxx while not all
3.07.02 are installed? I would say No. 
Code should check that. Can we test it? 

Non-superlibrarian could not login while not all updates were executed. But he
should! 
Superlibrarian is able to login. Clicking homepage goes to update page, but
clicking modules works fine. But I want homepage! I only like the warning if I
am logging in. 
I assumed that we allowed the situation now that not all dbrevs are executed,
but the code does not. Should be adjusted.

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.