Hi,

In the context of "store nulls", Phoenix seems to store empty arrays
and null arrays both as an empty byte array. We have a use case where
null means something different than empty.

I had a quick look at how arrays are serialized. The serialization
format starts by writing out the length of the array, hence I think it
is relatively easy to change the serialization of empty arrays into "a
byte array that represents an empty array by storing length=0" in
stead of "an empty byte array".

I can go ahead and provide patches, but I am wondering whether maybe
there is a reason why phoenix would not want to make the distinction
between null and empty?

This might also apply to strings?

Thanks
Jan

Reply via email to