[MDEV-26069] Outcome of sequence UPDATE is different on debug and release builds Created: 2021-07-01  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Debug, Sequences
Affects Version/s: 10.3, 10.4, 10.5, 10.6
Fix Version/s: 10.4, 10.5, 10.6

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Unresolved Votes: 0
Labels: None


 Description    

create sequence s;
 
update s set cycle_count = null order by cycle_count;
 
 
 
# Cleanup
 
drop sequence s;

All sequence fields, including cycle_count, are not-nullable. A release build returns the expected ER_BAD_NULL_ERROR error:

10.3 4a6e2d34 -DBUILD_CONFIG=mysql_release

 
query 'update s set cycle_count = null order by cycle_count' failed: 1048: Column 'cycle_count' cannot be null

But a debug build doesn't return any error:

10.3 4a6e2d34 -DCMAKE_BUILD_TYPE=Debug

 
MariaDB [test]> update s set cycle_count = null order by cycle_count;
 
Query OK, 0 rows affected (0.012 sec)
 
Rows matched: 0  Changed: 0  Warnings: 0

Reproducible on all of 10.3-10.6.
Generated at Thu Feb 08 09:42:30 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.