Fixed a really terrible bug! Took out the fixpriorities call in FillReserve. This is not necesary because the priorities are fixed up when the item is set to waiting in ReserveWaiting.
This commit is contained in:
parent
49e2aee04c
commit
91fc634cdd
1 changed files with 1 additions and 9 deletions
|
@ -65,7 +65,6 @@ sub FindReserves {
|
|||
(found <> 'F' or found is NULL)";
|
||||
}
|
||||
$query.=" order by priority";
|
||||
warn $query;
|
||||
my $sth=$dbh->prepare($query);
|
||||
$sth->execute;
|
||||
my $i=0;
|
||||
|
@ -123,12 +122,7 @@ sub CheckReserves {
|
|||
}
|
||||
}
|
||||
}
|
||||
warn "highest = $highest";
|
||||
$highest->{'itemnumber'} = $item;
|
||||
foreach my $key (keys %$highest) {
|
||||
warn "$key : $highest->{$key}\n";
|
||||
}
|
||||
|
||||
return ("Reserved", $highest);
|
||||
} else {
|
||||
return (0, 0);
|
||||
|
@ -202,8 +196,6 @@ sub FillReserve {
|
|||
$sth->execute;
|
||||
$sth->finish;
|
||||
$dbh->disconnect;
|
||||
# now fix the priority on the others....
|
||||
fixpriority($res->{'priority'}, $biblio);
|
||||
}
|
||||
|
||||
sub fixpriority {
|
||||
|
|
Loading…
Reference in a new issue