On Apr 28, 3:06 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> thought the behavior of this option was clear from Malcolm's initial
> description. It does support the 1,2,3 you specify. Which alternative
> would you prefer?
Maybe it's just me, but I just don't like a parameter that seems
boolean having different behavior for None than for False.
I would rather see two different parameters, e.g.::
.save([force_update=True|False, force_create=True|False])
That both default to False, and raise a ValueError when both are True.
Of course that's just me.
Cheers,
Mike
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
