On 07-08-2021 11:38, Dmitry Yemanov wrote:
07.08.2021 12:31, Mark Rotteveel wrote:
Currently, for blobs that are 4GB or longer, OCTET_LENGTH will
silently truncate the length. This means that a 4GB blob is reported
as length 0, a 5GB blob as 1,073,741,824.
It's not OCTET_LENGTH who's guilty,
07.08.2021 12:31, Mark Rotteveel wrote:
Currently, for blobs that are 4GB or longer, OCTET_LENGTH will silently
truncate the length. This means that a 4GB blob is reported as length 0,
a 5GB blob as 1,073,741,824.
It's not OCTET_LENGTH who's guilty, it's blob itself:
In memory:
ULONG blb_len
Currently, for blobs that are 4GB or longer, OCTET_LENGTH will silently
truncate the length. This means that a 4GB blob is reported as length 0,
a 5GB blob as 1,073,741,824.
Is this something that can be fixed? Or alternatively, would it be
possible to raise an error, warning, or maybe return
