On Thu, 2008-04-17 at 22:50 -0700, meppum wrote: > I searched around and couldn't seem to find an answer to this: does > the ORM make multiple trips across the wire to the DB if multiple > save() calls are made (assuming everything is wrapped in a single > transaction)? Or are all the calls batched together before commiting?
Each call is a database execute() call. So it will talk to the database each time. > If there are multiple trips is there a way to save a batch of objects > all at once (like a list of newly created models) in a single trip to > the database? I know that it wouldn't be a real BULK INSERT and that > it would be many INSERT INTO calls, but at least it would be more > efficient then traveling across the wire N times. Well, it's not that much more efficient. More or less the same amount of data is sent across the wire, for example. Anyway, this isn't possible without using custom SQL (i.e. writing the bulk insert or bulk update yourself). Regards, Malcolm -- Borrow from a pessimist - they don't expect it back. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
