#17957: ORM do not respect null=False if default db engine
interprets_empty_strings_as_nulls
-------------------------------------+-------------------------------------
Reporter: bhuztez | Owner: nobody
Type: Bug | Status: reopened
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by ramiro):
Also, this is part of documented behavior of Django with `CHAR`-based
model fields that include `''` among the possible valid values when using
Oracle to accommodate particular characteristics of such RDBMS.
See:
* https://docs.djangoproject.com/en/1.4/ref/models/fields/#null
* https://docs.djangoproject.com/en/1.4/ref/databases/#null-and-empty-
strings
--
Ticket URL: <https://code.djangoproject.com/ticket/17957#comment:4>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
