#29904: Not Null CharField Doesn't generate DB constrain on Oracle
-----------------------------------------+----------------------------
Reporter: Vackar Afzal | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 2.0
Severity: Normal | Keywords: Contraints
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+----------------------------
Given the following model:
{{{
class User(models.Model):
myField1 = models.CharField(max_length=20)
myField2 = models.CharField(max_length=20, blank=True)
myField3 = models.CharField(max_length=20, null=True, blank=True)
}}}
I would expect myField1 and field2 to have a db constraint assigned to
ensure that they are not null.
However all columns are nullable upon inspection via 3rd party db tool.
Is this by design, or a genuine bug?
--
Ticket URL: <https://code.djangoproject.com/ticket/29904>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/054.99a2f4d864bbc7c7162611ce02973cfe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
