#5219: Problems using syncdb with Oracle 10g - strange field names and null =
false ignored
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: jacob
Status: new | Component: Uncategorized
Version: SVN | Resolution:
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------+--------------------------------------------------
Comment (by ikelly):
Ignoring null=False for string-based fields in Oracle is intentional.
Oracle considers the empty string to be a synonym of null, so we coerce
null=True in order to be able to store the empty string.
We considered allowing this behavior to be overridden by explicitly
specifying null=False, but we decided it was more important that
null=False should have the same behavior regardless of whether it is
implicit or explicit. I'm open to other suggestions, though.
--
Ticket URL: <http://code.djangoproject.com/ticket/5219#comment:2>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
