#5219: Problems using syncdb with Oracle 10g - strange field names and null =
false ignored
-------------------------+--------------------------------------------------
Reporter: anonymous | Owner: nobody
Status: closed | Component: Uncategorized
Version: SVN | Resolution: wontfix
Keywords: | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------+--------------------------------------------------
Changes (by mboersma):
* status: new => closed
* resolution: => wontfix
Comment:
We document the Oracle null=True for CharField decision at
http://www.djangoproject.com/documentation/model-api/#null so in the
absence of contrary suggestions, I'm closing this bug.
--
Ticket URL: <http://code.djangoproject.com/ticket/5219#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
