We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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;
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 (1, '-5') insert into fk_t16 (id, col) values (1, '-5')
Now if you run the query - update fk_t15 set col = col * (col - (col)), you'll see that the foreign key constraints are broken.
update fk_t15 set col = col * (col - (col))
In the end, the data in the tables looks like -
select * from fk_t15; +----+------+ | id | col | +----+------+ | 1 | -0 | +----+------+ select * from fk_t16; +----+------+ | id | col | +----+------+ | 1 | 0 | +----+------+
Given in the description
main
all
No response
The text was updated successfully, but these errors were encountered:
-0
0
GuptaManan100
Successfully merging a pull request may close this issue.
Overview of the Issue
Consider the following schema -
Configure the keyspace such that Vitess is managing the foreign keys.
Insert the following data into the two tables -
Now if you run the query -
update fk_t15 set col = col * (col - (col))
,you'll see that the foreign key constraints are broken.
In the end, the data in the tables looks like -
Reproduction Steps
Given in the description
Binary Version
Operating System and Environment details
Log Fragments
No response
The text was updated successfully, but these errors were encountered: