Although formally, blob id 0 should not occur when reading blobs, in practice they can occur (and are always an empty blob). Currently Jaybird rejects attempts to read blobs with id 0 (depending on the access path, and some access paths only fail when assertions are enabled).
It was suggested by Vlad to always handle blob id 0 as NULL, but I think that goes a bit too far.
Instead, attempts to read blob id 0 should log a message on TRACE, and the proceed just like any other blob id.
This is related to #763
Although formally, blob id 0 should not occur when reading blobs, in practice they can occur (and are always an empty blob). Currently Jaybird rejects attempts to read blobs with id 0 (depending on the access path, and some access paths only fail when assertions are enabled).
It was suggested by Vlad to always handle blob id 0 as NULL, but I think that goes a bit too far.
Instead, attempts to read blob id 0 should log a message on TRACE, and the proceed just like any other blob id.
This is related to #763