Skip to Content.
Sympa Menu

grouper-dev - RE: [grouper-dev] need to remove paging from admin ui subject search

Subject: Grouper Developers Forum

List archive

RE: [grouper-dev] need to remove paging from admin ui subject search

Chronological Thread 
  • From: "GW Brown, Information Systems and Computing" <>
  • To: Chris Hyzer <>, Grouper Dev <>
  • Subject: RE: [grouper-dev] need to remove paging from admin ui subject search
  • Date: Sun, 04 Dec 2011 11:51:17 +0000

--On 04 December 2011 04:03 +0000 Chris Hyzer

Sorry, you need to put this in the soruces.xml for the source:

<!-- on a findPage() this is the most results returned -->
I have that. I also reduced the maxResults for the JDBC source to 100 so I could generate an error

Then you will see what I am seeing :)
Still not sure.

On the QuickStart database if I search for 'a' I get 134 results which page OK. If I specify the Example JDBC source and do the same search I get the 'too many results' error - so something is not consistent, but I'm still not sure what you are seeing that is wrong.


-----Original Message-----
From: GW Brown, Information Systems and Computing
Sent: Saturday, December 03, 2011 2:06
To: Chris Hyzer; Grouper Dev
Subject: Re: [grouper-dev] need to remove paging from admin ui subject

--On 03 December 2011 06:08 +0000 Chris Hyzer

The problem is that the admin UI used to get all subjects for a search
string, but that doesn't scale. The subject source interface doesn't
have support for paging (e.g. record count, and getting specific pages
/sizes… Im not sure this is possible in all subject source types)

Gary, think you have time to look at this in the v2.0 branch?

We need to remove paging buttons from subject search in admin ui, and if
there are too many members (the SubjectFinder.findPage() method will tell
you), then perhaps a message could be displayed that the user should
narrow their search, and it should also show whatever members it found
(e.g. the first 200 or whatever number is configured in the source).
I think you've already changed the code to deal with too many results - I
can provoke:
Error: Too many results, please narrow your search

It doesn't show any results - goes back to search screen - but I think
that is appropriate. Message might indicate the limit - but that appears
to be per source - SearchPageResult doesn't go to that level of detail -
not that you get on given the exception that is thrown.




GW Brown, IT Services

GW Brown, IT Services

Archive powered by MHonArc 2.6.16.

Top of Page