| Summary: | While upgrading all empty deleteditems.datelastborrowed turned deleteditems.timestamp to date of upgrade | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Wolfgang Moch <edv> |
| Component: | Installation and upgrade (command-line installer) | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Testopia <testopia> |
| Severity: | major | ||
| Priority: | P5 - low | CC: | fridolin.somers |
| Version: | 19.05 | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Bug Depends on: | 23081 | ||
| Bug Blocks: | |||
|
Description
Wolfgang Moch
2022-01-18 18:17:51 UTC
Hi, Maybe this comes from Bug 23081. It changes value of deleteditems.issues : $DBversion = '19.12.00.080'; if( CheckVersion( $DBversion ) ) { $dbh->do( "UPDATE items set issues=0 where issues is null" ); $dbh->do( "UPDATE deleteditems set issues=0 where issues is null" ); This impact on deleteditems.timestamp is an unwanted side effect. I don't know if it is technically possible to avoid it. It is technically possible if you include the timestamp in the update statement I think, set timestamp = timestamp or something like that. We have had the issue before... just don't remember the bug, it's been a longer while. Wish now I had remembered this one. A little too late to fix this update since the version in question is no longer maintained. Something to keep in mind still for new updates. |