On Thursday 23 February 2017 13:06:31 ludovic coues wrote: > Notice how Brian print self.rfid before and after affecting the new > value. The second print should display the updated data. As it is not > the case, I highly doubt save will change the value in db.
The two prints are different. How did you assert that they're not updated? > Ok, look like I misread the code when writing my previous reply. > Now I'm all curious about how did you find about the editable argument > and why you set it. > About your problem, django's BinaryField is not editable. Here is the > source for django 1.10.5 [1] > Notice how the init method override your argument ? I haven't checked > further but I'm pretty sure > it explain the issue you have noticed. Editability is a hint for forms, nothing more. Doesn't affect the operation of save, not even Model(not_editable_value='foo'). It merely means, that you will implement saving the value without the help of ModelForm. -- Melvyn Sopacua -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6429509.L4NeOCgRUK%40devstation. For more options, visit https://groups.google.com/d/optout.
