MX is interesting, to say the least.
Case II: cfsearch 'maxrows' attribute...
In my usual way, I run a full cfsearch once to get the maximum number of records, then
hold that and in the next/prev pages I only search for 10 records at a time...
<cfsearch collection="#Request.SearchCollections#" name="SearchSite" type="SIMPLE"
criteria="#URLDecode(Attributes.Criteria)#" startrow="#Attributes.StartRow#"
maxrows="10">
Starting at Attributes.StartRow = 1, we get 10 records... obvious really. But starting
at Attributes.StartRow = 11, we get naff all back, even though the recordcount of the
checkup search gave me somewhere in the region of 415 document.
Curious.
So I tried changing Attributes.Startrow to see what I got back.... a startrow of 2
gives me 9, startrow 5 gives me 6... and the pattern emerges. It appears that CFMX has
got maxrows buggered up and confused with an End Row
yippee bloody skippee!
Okay, so I've not started up K2 server, because basically... I can't be arsed with all
the faff. But if this is happening on the old verity, will cfsearch do the same on K2?
Has anyone else come across this problem? I haven't found anything in the bug list or
on the MM forums.
Yours
Detective Inspector Taz
