#14107: Problem with non-null fieds using Oracle Backend
---------------------------------------------------+------------------------
Reporter: mdpetry | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by ikelly):
* status: new => closed
* resolution: => invalid
Comment:
This is intended behavior, as noted in the docs:
> When using the Oracle database backend, the null=True option will be
coerced for string-based fields that have the empty string as a possible
value, and the value NULL will be stored to denote the empty string.
This is because Oracle treats the empty string and NULL as the same thing,
and a CharField can be used to store the empty string even with null=True,
blank=True. If you really want the column to be NOT NULL, you need to set
it manually.
--
Ticket URL: <http://code.djangoproject.com/ticket/14107#comment:3>
Django <http://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.
