#24307: Oracle Syncdb breaks trying to set NULL to column that already is NULL
-------------------------------------+-------------------------------------
Reporter: JorisBenschop | Owner: shaib
Type: Bug | Status: assigned
Component: Database layer | Version: 1.8alpha1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: oracle 1.8-beta | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shaib):
* owner: nobody => shaib
* status: new => assigned
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
It's a bug, I can easily reproduce it by just trying to migrate the
default project (created by `start_project`, with no changes except for
defining an Oracle database).
It happens, as the reporter said, because of Oracle silliness: On Oracle,
all `CharField`s are defined (in the database) null, because Oracle can't
tell the difference between null and an empty string. For Django 1.8, a
migration explicitly makes the `name` field null (it wasn't null before at
the Python level, nor on any other backend), and hence the failure.
--
Ticket URL: <https://code.djangoproject.com/ticket/24307#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/071.f12b1cbb0e1aedc536b2f785f663dc69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
