#24182: Bug with functional default and migrations
----------------------------+--------------------------------------
Reporter: arveitch | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by carljm):
I think that's right. This is a regression, but I think it was an
unavoidable one.
If this had been discovered before release, it certainly would have gone
into the backwards-incompatible section of the release notes for 1.7. Does
it make any sense to add it there now?
I also think we may need to consider whether there is any clean way, via
supported API, to detect the table-doesn't-exist yet case in a default
function like this one. Catching the exception is too broad, and asking
people to do their own raw SQL query to find out is quite ugly. Since this
is a backwards-incompatible regression I think if we can't fix it we would
ideally provide a clean, documented new alternative technique.
--
Ticket URL: <https://code.djangoproject.com/ticket/24182#comment:3>
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.c334e78ac9c72fbf215a3ddde11c54ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
