On 7/24/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > You're not the first to suggest insert() and update() methods that > explicity do SQL INSERT and UPDATE calls. I have a vague recollection > that a decision was made about adding these calls, but a quick search > in the ticket database didn't find the ticket that related to this > change. Feel free to do a more comprehensive search; the discussion > should be archived there (or, at the very least, in the > django-developers mailing list).
There was some discussion back when we were working around a session-collision bug, because some folks claimed that implementing separate INSERT and UPDATE methods would solve it, but at the time I lobbied for fixing the session bug and waiting for the QuerySet refactor to make a decision about INSERT/UPDATE :) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
