4 ms·

I don't see a problem with an O(n) algorithm to set some property on n objects.

• victorhooi 13y ago
  I think the issue is the call to save() (I assume this is meant to be outside the comma). Basically, it'll hit the database after each query.
  • philangist 13y ago
    I originally thought it might be that too, but it seems to me like you'll have to hit the database n times for n queries no matter what. Unless Django has some builtin batch save functionality.
    • victorhooi 13y ago
      Hmm, there's bulk_create(), introduced in Django 1.4, to create multiple new objects in one DB call. However, I'm not aware of anything that would do the same to update properties.