#23408: Automaticly created migration calls callable for default only once
----------------------------+------------------------------------
Reporter: Harper04 | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by Harper04):
Hi,
thanks for your time.
I would argue that this behavior is not intended as best practice to
create fields like "created_at" fields is to assign a callable.
Calling it only once during a migration is killing dynamic behavior. What
if the default value of this field is dependent on another one?
regards
Tom
--
Ticket URL: <https://code.djangoproject.com/ticket/23408#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.20b319204d596c28cbee087cd60c9f98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
