So, are cursors a way to avoid retrieving data sets that potentially are too large? Contact for example has the change to retrieve more than the allowed limit of records.
@PieterJacob - A batch size in batch Apex is limited to max 2K. Lets say you can process 4K records in a transaction you would need 2 jobs. With cursors just one job is enough. The idea is if you have a process that can run quickly use cursors. You can go upwards in that scope for cursors even beyond that 2K limit that batch has
Thanks!! really helpful content...Please keep posting
Happy that you liked the video.
Sir you are doing great it's very helpful
Thanks and welcome
So, are cursors a way to avoid retrieving data sets that potentially are too large? Contact for example has the change to retrieve more than the allowed limit of records.
Not only retrieve large data sets, bur process them efficiently by breaking into small manageable chunks.
@@TechnicalPotpourri and how does it distinguish from a Batch? Apart from having more freedom in the chunks you are processing using a cursor…
@PieterJacob - A batch size in batch Apex is limited to max 2K. Lets say you can process 4K records in a transaction you would need 2 jobs. With cursors just one job is enough. The idea is if you have a process that can run quickly use cursors. You can go upwards in that scope for cursors even beyond that 2K limit that batch has
@@TechnicalPotpourri Thanks a lot for your answer. I will test and try it out :).
Have a good day.
Is it advanced version of querylocator ?
No. It is a new feature.