#17957: If engine for default DB alias has interprets_empty_strings_as_nulls
(i.e.
Oracle) it affects DDL SQL for model fields null=False in other DBs
-------------------------------------+-------------------------------------
Reporter: bhuztez | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Ready for
Keywords: oracle | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* status: reopened => closed
* resolution: => fixed
Comment:
Fixed in 584e2c03376895aeb0404cc1fcc1ad24dfdbc58e
For the record: Alex spotted that the patch altered the way non-nullable
character fields are handled in sql/query.py. There were a couple of
field.null checks there, and those are now handled by is_nullable(field)
so that the old behavior is preserved. See
https://github.com/django/django/pull/19/ for more details.
--
Ticket URL: <https://code.djangoproject.com/ticket/17957#comment:13>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
