Home/ Questions/Q 580619
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T14:29:31+00:00

I think I’ve read somewhere that Django’s ORM lazily loads objects. Let’s say I

  • 0

I think I’ve read somewhere that Django’s ORM lazily loads objects. Let’s say I want to update a large set of objects (say 500,000) in a batch-update operation. Would it be possible to simply iterate over a very large QuerySet, loading, updating and saving objects as I go?

Similarly if I wanted to allow a paginated view of all of these thousands of objects, could I use the built in pagination facility or would I manually have to run a window over the data-set with a query each time because of the size of the QuerySet of all objects?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If the batch update is possible using a SQL query, then i think using sql-queries or django-orm will not make a major difference. But if the update actually requires loading each object, processing the data and then updating them, you can use the orm or write your own sql query and run update queries on each of the processed data, the overheads completely depends on the code logic.

    The built-in pagination facility runs a limit,offset query (if you are doing it correct), so i don’t think there are major overheads in the pagination either ..

    • 0