#24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL
-------------------------------------+-------------------------------------
Reporter: JorisBenschop | Owner: shaib
Type: Bug | Status: closed
Component: Database layer | Version: 1.8alpha1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: oracle 1.8-beta | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Shai Berger <shai@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ceadc94f09f0615e95146f9a42b711acfc14f40f"]:
{{{
#!CommitTicketReference repository=""
revision="ceadc94f09f0615e95146f9a42b711acfc14f40f"
Fixed #24307: Avoided redundant column nullability modifications on Oracle
Thanks Joris Benschop for the report, and Tim Graham for the tests.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24307#comment:6>
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/071.290b052b14e64efc13f169fd21744a7f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
