Patron Images Database update didn't hit
Maybe it's just me, but when I pulled down the patron images patch with the database create table it didn't hit the installer page to do the database update. I looked at the updatedatabase.pl file, and it seems that the patronimages update ended up with the same DBversion as the previous update. Maybe something should be done to make sure that doesn't happen. It seems like a tough problem to handle though. Could just skip a version number or two to leave space for other developers, but then the installer would have to check to make sure that previous updates were run for sure. That wouldn't be trivial to implement. Maybe have to leave things the way they are.
Maybe something should be done to make sure that doesn't happen. It
seems like a tough problem to handle though. Could just skip a version number or two to leave space for other developers, but then the installer would have to check to make sure that previous updates were run for sure. That wouldn't be trivial to implement.
Maybe have to leave things the way they are.
_______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
Would it be possible to start inserting some developer specific part (say, part of the MAC address in decimal form) into the DB version? This would at least make them unique. -- Jesse
Would it be possible to start inserting some developer specific part (say, part of the MAC address in decimal form) into the DB version? This would at least make them unique.
Basically I just have to check better when doing my QA on patches :) Ive fixed the problem and sent a patch up to the Release Manager. Chris
On Mon, Mar 3, 2008 at 6:39 PM, Michael Hafen <mdhafen@washk12.org> wrote:
Maybe it's just me, but when I pulled down the patron images patch with the database create table it didn't hit the installer page to do the database update. I looked at the updatedatabase.pl file, and it seems that the patronimages update ended up with the same DBversion as the previous update.
There's a patch in the queue to fix this. After it's committed you should be be able to rebase and the installer will pick it up. Regards, Chris -- Chris Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org
participants (4)
-
Chris Cormack -
Chris Nighswonger -
Jesse -
Michael Hafen