Summary: | (Bug 31314 follow-up) Placing a hold on a serial generates DBI Exception | ||
---|---|---|---|
Product: | Koha | Reporter: | Janusz Kaczmarek <januszop> |
Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | major | ||
Priority: | P2 | CC: | gmcharlt, jonathan.druart, nick |
Version: | 22.11 | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Janusz Kaczmarek
2023-02-27 21:38:52 UTC
In 22.11, apparently after applying bug 31314 (perhaps in conjunction with Bug 31306), placing a hold (from OPAC: opac-reserve.pl) on a serial record (i.e. a MARC 21 record with 942 $s set) generates runtime error and produces in opac-error.log the following info: DBI Exception: DBD::mysql::st execute failed: Column 'biblionumber' in where clause is ambiguous It seems that this is caused by the presence of 'serialid.publisheddate' in the line: order_by => [ 'serialid.publisheddate', 'me.enumchron' ] in Koha::Items::search_ordered. |