Bug #114208 table update fails with an "Column xxxx cannot be null" error.
Submitted: 4 Mar 15:41 Modified: 5 Mar 4:10
Reporter: Wen Liang Chang Email Updates:
Status: Analyzing Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.31, 8.0.32, 8.0.33, 8.0.34, 8.0.36 OS:Windows (10, 11)
Assigned to: MySQL Verification Team CPU Architecture:Any

[4 Mar 15:41] Wen Liang Chang
table design will all columns type not null, Global and Session sql_mode="".
Running an update SQL script on existing data on "column_a" will prompt "Column column_b cannot be null" error. this causes the inability to run SQL update script using MySQL Workbench's latest version.

issue started from Version 8.0.31 till the latest.

The workaround is to install MySQL Workbench Version 8.0.30

How to repeat:

AWS Aurora MySQL Serverless V1 [version 5.7.12-log(MySQL Community Server(GPL)]
Global sql_mode="".

table1 with all columns defined int NOT NULL, varchar NOT NULL, ...

running SQL update script like:

UPDATE `table1` `t1`
JOIN `table2` `t2` ON `t1`.`id`=`t2`.`t1_id`
SET `t1`.`column_a`="value"

error prompt stated that the other column cannot be null.

no issue on MySQL Workbench Version 8.0.30