Value of NOT_PROVIDED might collide with real data
|Reported by:||Antti Kaihola||Owned by:||Adrian Holovaty|
|Component:||Database layer (models, ORM)||Version:|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
In django.core.meta.fields, NOT_PROVIDED is defined as
# Random entropy string used by "default" param. NOT_PROVIDED = 'oijpwojefiojpanv'
Although extremely unlikely, this string could appear as a default value in a model and be interpreted as if no default value was provided.
Is there something preventing the following:
class NOT_PROVIDED: pass
Or are there some control characters in the range chr(0..31) which don't make sense in the database backend side and could be used here?