Context Navigation

Changes between Initial Version and Version 1 of Ticket #29904, comment 3

initial	v1
3	3	Nullability has nothing to do with the representation of the null, just wether or not the field may be null.
4	4	i.e If a column has a not null constraint, it should not accept an empty string or 'Null'
5		With Django's current behaviour, since declaring a field as not null has no effect, both 'Null' and '' may be inserted without issue.
	5	With Django's current behaviour, since declaring a field as not null has no effect, both 'Null' and blank strings may be inserted without issue.
6	6	I would argue that this is a broken design. How are raw queries enforced, or additional clients that have no knowledge of the Django's internal checks and conversions?
7	7	If Django needs to do internal checks, it should use the value of 'blank' and not 'null' to be consistent with other backends. Oracle supports not null constraints, why not exploit that?