> If there are any, then I would expect it'd handle them just as it does > without the flag. The problem is (at least in my eyes) that Django > should not be guessing, and especially should not be doing an extra > query, when you are explicitly saing update or create on an object.
Django *would* be guessing if it relied on an is_stored attribute, and failed to validate that when it came time to save. Though I do agree, an explicit create should just do an insert. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
