On Aug 31, 2:39 am, David Cramer <[EMAIL PROTECTED]> wrote: > Intially is_stored is set to None. When you do a .get or .create it > would then set it to True. When you delete, it would set to False. > > A big that this does solve, beyond fixing my multiple pks, is explicit > calls. > > - Calling .create would no longer do a select + insert (or update) if > you had a pk attribute set. > - Calling .create would error if the row already exists.
Am I the only one seeing concurrency issues everywhere in this thread? -- Ludvig Ericson --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
