While I’m hardly entitled to a vote, it is almost impossible to find a use case where making a concatenation with a NULL a NULL is useful. NULL should be interpreted as “there ain’t nothing there” rather than a poison pill for other contexts.
In Amorphous, concatenation of a NULL treats the NULL as an empty string, but then in Amorphous I am king and dictator. But, for the record, Ann and I disagree on this. On Thu, Aug 11, 2022 at 11:58 AM Vlad Khorsun <hv...@optima.com.ua> wrote: > 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. > > > I had hoped for something more solid, so I could add that as an > explanation when documenting it in the language reference. > > 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. > > > PS You mailed this to me privately instead of to the list. > > Sorry, hope you are not suffer too much because of it ;) > > Regards, > Vlad > > > > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel > -- Jim Starkey
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
