Datasets may be in the thousands, or millon rows...
The problem I have with delegating sorting and querying to providers is that paging gets really tricky.
my @rows;
for my $provider( qw/Provider1 Provider2 Provider3/ ) {
push @rows, $provider->search(
query=>..., sort=>...,
page=>1, rows=>10
);
}
# now I may end up with 30 rows for page 1
# but the client grid expects 10, so let's cut it down...
@rows = @rows [ 0..9 ];
So, ideally, the "collection manager object" should work with this algorithm:
- Ask each provider to search for a certain query and sort
- Ask for a row from each provider starting at a given page
- Is the page complete? Then call any external filters callbacks.
- External filters dropped rows? Then keep fetching until page is complete again.
- Sort the combined rows
- Return resulting array, but keep track of the current paging state
--Miguel
Code tags added by GrandFather
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.