Re:Algorithmic Interviewing – Optimizing to Hire the Wrong D...
by philangist on Monday September 02, 2013 @02:52AM
(#6313775)
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.
Re:Algorithmic Interviewing – Optimizing to Hire the Wrong D...
by victorhooi on Monday September 02, 2013 @08:26AM
(#6314808)
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.
Basically, it'll hit the database after each query.