#22738: Schema migration: test_add_field_temp_default_boolean
--------------------------------------+------------------------------------
Reporter: maxi | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by shaib):
Yes, and it passes as well.
I had hoped for a more "surgical" solution, where each backend gets to
specify exactly what is expected here; the current suggestion is a little
blunt in this regard, and Oracle stays special-cased in the test, which
I'd rather avoid; but the suggestion does solve the problem in an
acceptable way, IMO.
--
Ticket URL: <https://code.djangoproject.com/ticket/22738#comment:9>
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/062.4541d1c708660ba8c8727384dd4321b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.