#23408: Automaticly created migration calls callable for default only once
----------------------------+------------------------------------
Reporter: Harper04 | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: invalid
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 stavros):
I do indeed want unique values per row, and will populate them myself,
but, in that case, I don't want Django setting the default and having me
wonder down the line why the rows for which I didn't specify a value have
a default of 2014-06-24. The correct behavior there would be to ignore the
default completely, since there's no reasonable use case where it's
supposed to call the callable once and use it for all the columns.
--
Ticket URL: <https://code.djangoproject.com/ticket/23408#comment:5>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.ed97badd2a87654e3e846c15b79463d5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
