On Tue, 2009-03-10 at 14:19 +1100, Malcolm Tredinnick wrote: > On Mon, 2009-03-09 at 15:46 -0600, Ian Kelly wrote: [...] > > There may also be an argument for removing the seemingly redundant > > get_db_prep_save call from save_base. > > Which would break large amounts of code, so let's not do that. :-)
Whoops. My bad. Re-reading, trying to work out the test case, I see you're talking about the one in the update path, not the "save initially" path. That seems reasonable, since we have to do it in UpdateQuery. I'm back on track now. Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
