Comments on: Using Aggregate Functions

By: Jason Venable

Jason Venable — Wed, 31 Mar 2010 18:10:56 +0000

@Brett Kahnke

This message only appears with IE browsers.Google “disable ie mixed content warning” and it should show you how to disable this warning.

By: Jason Venable

Jason Venable — Wed, 31 Mar 2010 18:01:50 +0000

Okay. I think my original statement was correct. These queries are limited to 10,000 rows. I don’t know why but I swear this type of query was working earlier but now it is failing to many query rows.

AggregateResult[] groupedResults = [SELECT Account.Industry, AVG(Amount)aver FROM Opportunity group by Account.Industry];

As I originally stated this is because the database must query every row to calculate the average.

By: Brett Kahnke

Brett Kahnke — Wed, 24 Feb 2010 17:52:21 +0000

Sorry, silly question. I know why – it’s caused because the google charts don’t support https: But, how do you deploy this to your users without driving them nuts? Thanks again

By: Brett Kahnke

Brett Kahnke — Wed, 24 Feb 2010 17:19:20 +0000

Working great for us. Thanks! Any idea why this code would cause IE to have the non-secure information pop-up every time the Campaign is viewed?

By: Evan Callahan

Evan Callahan — Tue, 16 Feb 2010 17:31:58 +0000

Great post. FYI, I am working on these features in the IDE – all you have to do is open the meta…xml file and change the version to 18.0, and then you are able to work on the features there.

By: Mike Leach

Mike Leach — Sat, 13 Feb 2010 23:22:05 +0000

Nice post. I share the pain of only being able to develop for v18 features in the browser.

By: Wes

Wes — Thu, 11 Feb 2010 10:05:46 +0000

Nice work Scott, these will be incredibly useful going forward.. and to some degree in making legacy code more efficient *grumble grumble*.

By: Jason

Jason — Wed, 10 Feb 2010 18:55:24 +0000

Actually I am wrong. Something like this:

AggregateResult[] groupedResults = [SELECT Account.Industry, AVG(Amount)aver FROM Opportunity group by Account.Industry];
for(AggregateResult a : groupedResults){
system.debug(a.get(‘Industry’));
system.debug(a.get(‘aver’));
}

…according to the debug log limits is only returning 1 row even though it says 152 rows where returned. I’m guess the 152 is the number of Industries.

It would appear using group by is the key to controlling row limits.

Something like this will cause the too many query rows exception:

AggregateResult[] groupedResults = [SELECT AVG(Amount)aver FROM Opportunity];

By: Jason

Jason — Wed, 10 Feb 2010 18:26:47 +0000

Because to get the number (avg, count, sum) database must query all of the rows.

Min and Max are sort of silly as you could always get these by using order by asc / desc and limit 1.

By: Scott Hemmeter

Scott Hemmeter — Wed, 10 Feb 2010 18:22:55 +0000

@Jason, does a lot of that go away with Spring 10 when collections have no limit? Why would there be a 10,000 row limit on a query like this when all you are retrieving is a number?

By: Jason

Jason — Wed, 10 Feb 2010 18:19:12 +0000

One thing to watch out for is this line:

AggregateResult[] groupedResults = [select Status, count(Id) from CampaignMember where CampaignId = :camp.id group by status];

is still governed by the query row limit (ie 10000 for VF pages) and what makes this even trickier is that you cannot use the limit clause on a Aggregate query. And what makes this even more dangerous is that SOQL limit exceptions cannot be caught and handled.