So the PR followed here : https://github.com/django/django/pull/7515
The PR is based on the idea defined by Ben just above.
It raised 2 questions which I'd like to bring to your attention :
1. When inserting or updating a model instance that contains one or more
readonly fields, should we fetch
On 7 Nov 2016, at 13:44, Joachim Jablon wrote:
> My own personal opinion: 1. refesh by default, add an argument to
> "model_instance.save()" to opt-out. 2. readonly
I agree.
--
Aymeric.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contri
There's a fragment in the policy list of the abstract:
rough consensus among the community and core team that the chosen dependency
I assume that phrase should end with "is needed"
-Thomas
On Sat, Nov 5, 2016 at 9:20 AM Patryk Zawadzki wrote:
> W dniu sobota, 5 listopada 2016 13:24:28 UTC+
