Bug Report: Vitess Allows updating a child to value -0 when the parent has 0 if the update is done via an arithmetic expression

[GuptaManan100]

Overview of the Issue

This bug was found by the fuzzer introduced in #13980.

Consider the following schema -

create table fk_t15
(
    id bigint,
    col varchar(10),
    primary key (id),
    index(col)
) Engine = InnoDB;

create table fk_t16
(
    id bigint,
    col varchar(10),
    primary key (id),
    index(col),
    foreign key (col) references fk_t15(col) on delete cascade on update cascade
) Engine = InnoDB;

create table fk_t17
(
    id bigint,
    col varchar(10),
    primary key (id),
    index(col),
    foreign key (col) references fk_t16(col) on delete set null on update set null
) Engine = InnoDB;

create table fk_t18
(
    id bigint,
    col varchar(10),
    primary key (id),
    index(col),
    foreign key (col) references fk_t17(col) on delete cascade on update cascade
) Engine = InnoDB;

create table fk_t19
(
    id bigint,
    col varchar(10),
    primary key (id),
    index(col),
    foreign key (col) references fk_t17(col) on delete set null on update set null
) Engine = InnoDB;

Configure the keyspace such that Vitess is managing the foreign keys.
Insert the following data into the two tables -

insert into fk_t15 (id, col) values (2, '-0');
insert /*+ SET_VAR(foreign_key_checks=0) */ into fk_t16 (id, col) values (3, '5'), (4, '-5')

Now if you run the query - update fk_t16 set col = col * (col - (col)) where id = 3,
you'll see that Vitess allows this query even though MySQL rejects it.

Linked to the bug #14523

Reproduction Steps

Given in the description

Binary Version

main

Operating System and Environment details

-

Log Fragments

No response