One Context and New Limits For Governors in Spring ‘11

The title might be a mouthful, but this update in Spring ‘11 will be a welcome change to anyone who has spent a late night on a conference call with ten other developers trying to untwine the debug logs to see which trigger it is that is taking 7 out of the 20 precious DML statements and bringing down an application.

With Spring ‘11, triggers are no longer held to their own context and will have the same DML limits as everything else you’re coding.  Additionally, the limit itself is raised to 150 statements, so even your controllers will have some more breathing room.

And if that wasn’t enough – the maximum number of rows that SOQL can handle will go from 10,000 to 50,000.  One of the things I love about developing on Force.com is that it seems every year, it makes tricks I used last year to handle such limits obsolete, but this year seems like the spring release is going the extra mile.

Find out more about this in detail by checking out the release website, and sign up for the Spring ‘11 webinar to see the changes in action and chat with us directly about them.

tagged , , , , Bookmark the permalink. Trackbacks are closed, but you can post a comment.
  • http://tehnrd.com Jason

    And 100 SOQL queries! I probably hit this limit in a trigger context more than any other because with triggers I am usually retrieving information related to the given record, not updating/inserting other records.

  • http://corycowgill.blogspot.com Cory Cowgill

    The governor limits in this release are awesome and will resolve a lot of issues. It’s the most powerful feature in this release in my opinion as it impacts the core code for so many custom applications.
    If you told me a year ago I’d be able to do 50,000 records in a Trigger context I’d say thats never going to happen. So much so in fact I had to run a trigger in my pre-release org and look at the limits logs to actually believe it! Sure enough, it was there! AWESOME! WOOT!