Daniel Black added a comment - 2022-05-13 01:52 Nice use of dbfiddle's comparison. Copying here for preservation's sake: CREATE TABLE entry ( `id` int unsigned PRIMARY KEY AUTO_INCREMENT, `field1` varchar (200), `field2` varchar (200), `gen_aux1` tinyint unsigned NOT NULL , `gen_aux2` tinyint unsigned NOT NULL , `gen` tinyint unsigned GENERATED ALWAYS AS (`gen_aux1` AND `gen_aux2`) VIRTUAL, FULLTEXT INDEX `idx_text` (`field1`, `field2`) );   INSERT INTO entry(`field1`, `field2`, `gen_aux1`, `gen_aux2`) VALUES ( 'hello' , 'world' , 0, 1), ( 'hello lorem' , 'hello ipsum' , 1, 1);   SELECT * FROM `entry`;   # gen is NULL in MariaDB SELECT * FROM `entry` WHERE MATCH(`field1`, `field2`) AGAINST ( 'hello' IN NATURAL LANGUAGE MODE); actual results id field1 field2 gen_aux1 gen_aux2 gen 2 hello l.. hello ip. 1 1 NULL 1 hello world 0 1 NULL expected results (MySQL 5.7.35, 8.0.27) id field1 field2 gen_aux1 gen_aux2 gen 2 hello l. hello ip.. 1 1 1 1 hello world 0 1 0

Marko Mäkelä added a comment - 2022-05-13 05:30 - edited If I remember correctly, the virtual column implementation in MySQL 5.7 allows virtual columns to be declared NOT NULL , while MariaDB does not. I suppose that the motivation of that design decision is to allow evaluation errors to be mapped to NULL values. ( INSERT in MariaDB does not evaluate virtual columns, unless they are indexed . Hence, a virtual column expression like 1/x does not work as a substitute for a constraint CHECK x!=0 .) Without looking at the code, I would guess that here the problem is that the values of virtual columns are simply not computed in the relevant code path, and a ‘default’ value of NULL is being reported.