On 3/15/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > The point is: It's not possible to extend the session in a > upwards-compatible way, because there's no way to make sure > that INSERT is used when you need to set the pk before save().
Again, I'm not disagreeing with the INSERT/UPDATE suggestion, I'm just saying that a change to the model API should not take place while we have a bug hanging over our heads; let's fix the random-number collision, reduce the window between getting a session key and saving the session, and then look at model saving once we can breathe again. Making a design decision like this under the pressure of a bug that we all want fixed is not a good idea ;) -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
