hugo wrote:
>I would be +1 on this. Especially since transactions are already in
>m-r, so we won't have to worry about multiple save points playing havoc
>with our database connection.
>
I'd say -1. For it's not about database it's about what is expected
behavior. Currently I'm never sure what causes save and what doesn't.
For example there are two seemingly similar ways of adding dpendent
object (in pre m-r syntax):
poll.add_choice(...)
and
choice=choices.Choice(poll_id=...)
But the first one does an implicit save().
Also I can't remember for the hundreth time if save_foo_file() also
saves its object or not. I always go to the source to check it out :-)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
