Patron search code does not recognize empty patron group
Bug #1537812 reported by
Mike Rylander
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Triaged
|
Medium
|
Mike Rylander |
Bug Description
In some situations, the patron search code will send an empty or NULL patron group string as part of the search parameters. This is not recognized and causes long (to the point of timing out) search calls. This can be avoided by checking for the presence of a search value.
Changed in evergreen: | |
milestone: | 2.next → 2.10-beta |
Changed in evergreen: | |
milestone: | 2.10-beta → 2.10-rc |
Changed in evergreen: | |
milestone: | 2.10-rc → none |
Changed in evergreen: | |
milestone: | none → 2.next |
milestone: | 2.next → none |
no longer affects: | evergreen/2.8 |
no longer affects: | evergreen/2.9 |
Changed in evergreen: | |
milestone: | none → 2.next |
no longer affects: | evergreen/2.10 |
no longer affects: | evergreen/2.11 |
Changed in evergreen: | |
milestone: | 3.next → none |
To post a comment you must log in.
And, here's the branch:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ miker/lp1537812 -patron_ search_ timeout
It is not clear where the long-running queries are coming from, though it is
likely either the actual patron search interface or from the duplicate check
performed during patron registration. Therefore, testing is made particularly
difficult.
This is backport-able, and should be, IMO.