#29904: Not Null CharField Doesn't generate DB constraint on Oracle
------------------------------+--------------------------------------
Reporter: Vackar Afzal | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 2.0
Severity: Normal | Resolution: invalid
Keywords: Contraints | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => invalid
Comment:
I don't know much about the design decision but it dates to the beginning
of the OracleBranch in 2006. If you want to revisit that decision, you
should make a proposal on the DevelopersMailingList so it'll reach a wider
audience. This should include at least a description of the change you're
proposing and the backwards compatibility considerations. If you can put
together a patch to demonstrate that your idea is feasible and passes
Django's test suite, that will no doubt help your proposal. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/29904#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.5f6e36447d908e2b945fff1286c690cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
