Summary: | warning: "sort (...) interpreted as function" when running updatedatabase | ||
---|---|---|---|
Product: | Koha | Reporter: | Victor Grousset/tuxayo <victor> |
Component: | Installation and upgrade (command-line installer) | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | dcook, jonathan.druart, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 38664 | ||
Bug Blocks: |
Description
Victor Grousset/tuxayo
2025-02-11 22:04:04 UTC
So I guess it can be fixed either by looking at that weird perl behavior. Or by fixing that old DB rev so it actually gets the max_date. Assuming that's correct functionally. A fix might change the code enough to avoid the weird warning. Just reversing the sort with { $b cmp $a } avoids the warning ^^" my ($max_value2) = sort { $b cmp $a } ( $var_with_long_name_1, $var_with_long_name_2, $var_with_long_name_3 ); ---- Should severity be major because it might cause doubt on whether upgrade failed or worked? |