Closed gsbelarus closed 5 years ago
Both blob read and write has problems with data > 64KB. I don't known why you say write
succeded.
However, I think read
not necessarily returns in one go the total bytes you're requesting. You should read in a loop until it returns -1
representing the stream end. That could also be parameterized with a option to fully read the requested size in one call.
I thought that write succeded because there were no error thrown during method call.
Is it limitation of node/driver, fbclient library or fb server itself?
In my test the method throwed. Firebird has the limitation, each segment can have a maximum of 64KB, so we should call it spliting the buffer.
We have a strange problem. Below is a test. It works fine with BLOB string of 65 000 bytes but when size of BLOB is increased up to 650 000 bytes it fails. It is written without any problem but subsequent SELECT statement could read only 60 176 bytes of it.
We test it with FB3 embedded and Nodejs 11.12.