Bug 6127 - Setting library on patron search brings back all patrons regardless of search
Summary: Setting library on patron search brings back all patrons regardless of search
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: master
Hardware: All All
: P5 - low normal (vote)
Assignee: Kyle M Hall
QA Contact: Bugs List
URL:
Keywords:
: 6500 (view as bug list)
Depends on:
Blocks: 6253
  Show dependency treegraph
 
Reported: 2011-04-07 21:20 UTC by Liz Rea
Modified: 2012-10-25 23:09 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Liz Rea 2011-04-07 21:20:39 UTC
Steps to duplicate:

Enter a patron name in the patron search box
Click the [+]
Select a specific library
Click Search

All patrons from the selected library are returned alphabetically.
Comment 1 Liz Rea 2011-04-07 21:23:33 UTC
Confirmed this still happens even if you set the library first, then type in your search
Comment 2 Ian Walls 2011-04-19 17:38:20 UTC
This is because the branchcode or patron category "limit" is being passed to Search() in a way that implicitly OR's the results, rather than ANDing them.  Unfortunately, with the currently implementation of Search(), this cannot be fixed without losing search on Extended Attributes.
Comment 3 Nicole C. Engard 2011-06-25 21:04:53 UTC
The patch for 6513 has code that will solve this problem.
Comment 4 D Ruth Holloway 2011-11-22 16:27:09 UTC
*** Bug 6500 has been marked as a duplicate of this bug. ***
Comment 5 D Ruth Holloway 2011-11-22 16:28:31 UTC
I'm also observing this behavior if you limit by patron category!
Comment 6 Liz Rea 2011-11-22 21:47:28 UTC
This should have been fixed by bug 6253, and I do not observe this behavior in master.
Comment 7 Liz Rea 2011-11-28 16:36:21 UTC
Fixed by development for bug 6253.