Hi, Following up on the discussion on: https://groups.google.com/forum/?fromgroups=#!topic/django-developers/DUQtBrM2iTs
I'd like to start a clear discussion about re-opening ticket 901. https://code.djangoproject.com/ticket/901 Ticket 901 was marked 7 years ago as won't fix and has been subject of debate since. I must say that I for myself was looking for such a method until I found that foo = Foo.objects.get(id=foo.id) would work; which did not seem obvious to me then and now. Brandon put forward an argument, which is: reload() would cover an important use case that did not get a hearing in the above discussion: that you might already have handed the object off to some other library, which is keeping a reference from somewhere deep in its data structures for use when you make a final call to it. If one or more data structures that are being built already hold the object, then it is not reasonable to have to track down the object and try to swap in a new copy everywhere. There should be a simple way to have the existing object's attributes update in-place. and Anssi thinks it is a good idea to implement this. My question is, can we please re-open this ticket and/or discuss here what are the benefits and drawbacks of having a method reload() ? For clarity, this question is in no way meant to be offensive. And if you want to discuss personal views about this ticket or the behaviour of django community in general, I politely request you to do so at: https://groups.google.com/forum/?fromgroups=#!topic/django-developers/DUQtBrM2iTs Best regards, Wim -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
