Thanks for the reply Jacob, But I intentionally posted it here. Reason: I am *not* asking about how to use Django, the document is (mostly) excellent! But I accept any comments on my usage. :-)
I actually want to point the Django developers to the implementation of Model.save() and am trying to suggest an internal (overridable) implementation detail* which makes more sense (well, to me anyway). I do not intend to make a "feature request" ! (it would add feature, but that doesn't happen to be my main concern :-) ) And so, I think that my post belongs on this mailing-list. Am I wrong? Arvind *which just means, refactoring save() to save() and add() which will keep it compatible. Otherwise, may I ask why present save() was chosen over save() and add() ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
