Context Navigation

Changes between Initial Version and Version 1 of Ticket #29656, comment 10

initial	v1
2	2
3	3	- Note that I did not clear any fields, as mentioned in the simpler example provided (ie. `IntegerField(blank=True, default=0)`). '''Rangefields with a default value have ''blank'' inputs, so there is nothing to clear'''. It's not 'user error', really.
4		- Without a fix for this, using rangefields with modelforms would a) require either `null=True` all the time to 'work', or b) field validation to always have either upper or lower bound value set (so, unable to have unbounded rangefield), or c) the inability to use modelforms with models containing rangefields
	4	- Without a fix for this, using rangefields with modelforms would a) require either `null=True` all the time to 'work', or b) field validation to always have either upper or lower bound value set (so, unable to have unbounded rangefield, but only when using a modelform to save), or c) the inability to use modelforms with models containing rangefields
5	5	- Lastly, as I mentioned in my comment above, with `null=True` as a 'fix' it would require using `if instance.age_range is not None` everywhere you wanted to access PostgreSQL `Range`-based properties like `.lower`, etc. This would make code incredibly verbose.
6	6