Em 11/08/2022 12:58, Vlad Khorsun escreveu:
11.08.2022 17:26, Mark Rotteveel wrote:
On 11-08-2022 16:21, Vlad Khorsun wrote:
11.08.2022 17:10, Mark Rotteveel wrote:
Why was this NULL behaviour chosen?
To make BLOB_APPEND more convenient for users.
I don't understand how using a different NULL behaviour then standard for
operations in SQL/Firebird is convenient.
There is no standard defined operation for appending blobs, afaik.
To me it sounds like something that will result in confusion because of the
difference with normal concatenation, but OK.
The BLOB_APPEND is not CONCATENATION, it is non-standard function with
custom semantics.
As well many of our system functions, and we choose to implement the
standard behavior on them.
This remember-me JavaScript:
> null + null
0
> 'null' + null
'nullnull'
The answer is the same - for user convenience. When I want to append
something to the
already existing blob, I doesn't expect to destroy my blob just because
nothing is
appended to it.
It's is inconsistent, and I do not see that as convenience.
Some user would think the convenience would be to treat it as strings
('null', 'NULL', 'Null').
Adriano
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
