| Summary: | Database update makes returned items show as checked out in circulation history | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Katrin Fischer <katrin.fischer> |
| Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | gmcharlt, kyle |
| Version: | Main | ||
| 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: | |||
The database update for 20.11.03 caues 2 issues: * It updated the timestamp to the time of the update and didn't preserve the previous one. * The NULL values show up in the circulation history as still checked out, I asusme the template checks for content of the field after doing a union of issues and old issues. And an emptry returndate = still checked out (staff interface) The NULL is ok, the timestamp can't be saved... but we could make the template smarter. $DBversion = '20.11.03.002'; if( CheckVersion( $DBversion ) ) { sanitize_zero_date('aqorders', 'datecancellationprinted'); sanitize_zero_date('old_issues', 'returndate'); NewVersion( $DBversion, 7806, "Remove remaining possible 0000-00-00 values"); }