lastcomment=1 can cause excessive row count

[GoogleCodeExporter]

Full description at:

http://www.mediawiki.org/wiki/Extension_talk:Bugzilla_Reports#.22Warnings_Were_G
enerated_..._Report_Truncated_Count_Greater_than_Max.22.2C_etc...

Original issue reported on code.google.com by mfeld...@vigil.com on 18 Aug 2009 at 11:16

[GoogleCodeExporter]

Original comment by ian.homer@gmail.com on 12 Dec 2009 at 10:00

• Added labels: milestone-1.2

[GoogleCodeExporter]

We're migrating our bug database from Test Track, and have imported them into
bugzilla with hopes of integrating into our in-house wiki. I have created a 
report
which returns only two records (which agrees with Test Track), keeping it 
simple and
specifying only the component name. Works fine until I add 'lastcomment=1', at 
which
point I get the above message and only the first record.

Since I can link to the actual bugzilla listing, losing the details is not a big
deal, but the 'hover bubble' is a cool feature and it would be nice to have it 
working.

I have tried bumping up the $maxrowsFromConfigDefault (to as much as 1000!) but 
while
this allows the report to complete and display both records, I still get the 
message.
These entries have A LOT of text in their description fields, but there are 
only two
actual records. Is this a bug, or just new user error?

A great extension - much simpler than writing out all the queries using 
SQL2wiki or
the like.

Thanks! Mickeyf

Oops - I discovered the 'troubleshooting' section at the bottom of the page. I 
have
pasted the SQL into phpMyAdmin, it does not generate any errors, but does 
generate
1362 rows. In the log I note that of the 1362 rows generated, apparently two are
being pulled out for rendering.

    That looks like a bug. The report truncation is designed so that an administrator
can put a cap on how big reports can get, but given that you've upped the
$maxrowsFromConfigDefault AND that the behaviour only happens when you add
"lastcomment=1" then it's clearly not behaving well. It might be that the 
counting of
the numbers of rows is amiss since this may be counting all the rows with all 
the
joins (of which only a couple of rows are relevant for your report). Log it @
http://code.google.com/p/bugzillareports/issues/list and I'll review this area 
of the
code --Ian Homer 22:57, 18 August 2009 (UTC) 

Original comment by ian.homer@gmail.com on 6 Jan 2010 at 12:00

[GoogleCodeExporter]

Original comment by ian.homer@gmail.com on 6 Jan 2010 at 12:26

• Added labels: Priority-High
• Removed labels: Priority-Medium