On 7/15/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > I just spotted the new "raw save" functionality added in > http://code.djangoproject.com/changeset/5658 . Aside from the fact > that (to my knowledge) this wasn't discussed on the mailing list and > seems to be a large enough addition that should have merited some > discussion (it's a new argument to save(), for crying out loud), the > documentation is a bit less than adequate.
The reason I didn't raise it for discussion is that it didn't hit my radar as something that would be considered a significant change. Yes, it's a new argument to save, but it is transparent to all existing uses, and it serves to provide a mechanism to disable a piece of functionality that is already quite well factored out (i.e., pre-save processing), but causes major problems when you expect data to be interpreted literally (such as in test fixtures). Obviously I misread the significance - apologies for that. > This begs the question, "Which pre-save processing would happen if I > *don't* use a raw save?" And there's nowhere in the documentation that > provides a definitive list of pre-save processing. It's almost worse > to have this documentation *unfinished* than it would be to leave this > undocumented. > > Russell, as this is your feature addition, could you write that up? I've improved the text in [5700]. Further suggestions welcome. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
