It might make sense to support undefined values when using explicitly-mapped managed objects.
Currently when there is a property mapped to a database column, it can have value or be NULL. The question is whether we can support undefined as well - e. g. by having configuration that will treat NULL as undefined.
This might bring better compatibility between explicit and generic object mapping. In case people would want to support both NULL and undefined, the only solution is to have JSON type property mapping.
This issue has been created based on #202 .
It might make sense to support
undefinedvalues when using explicitly-mapped managed objects.Currently when there is a property mapped to a database column, it can have value or be NULL. The question is whether we can support undefined as well - e. g. by having configuration that will treat NULL as undefined.
This might bring better compatibility between explicit and generic object mapping. In case people would want to support both NULL and undefined, the only solution is to have JSON type property mapping.
This issue has been created based on #202 .