Added test case to show that we get a warning from CHECK TABLE if we force...

Added test case to show that we get a warning from CHECK TABLE if we force auto_increment value to 0

mysql-test/suite/maria/r/maria.result

@@ -22,6 +22,17 @@ CHECK TABLE t1;
 Table	Op	Msg_type	Msg_text
 test.t1	check	status	OK
 drop table t1;
+create table t1 (a int primary key auto_increment) engine=aria;
+insert into t1 values (1);
+update t1 set a=0 where a=1;
+check table t1;
+Table	Op	Msg_type	Msg_text
+test.t1	check	warning	Found row where the auto_increment column has the value 0
+test.t1	check	status	OK
+select * from t1;
+a
+0
+drop table t1;
 create table t1 (a tinyint not null auto_increment, b blob not null, primary key (a));
 check table t1;
 Table	Op	Msg_type	Msg_text

mysql-test/suite/maria/t/maria.test

@@ -41,6 +41,16 @@ INSERT INTO t1 VALUES ('WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
 CHECK TABLE t1;
 drop table t1;
 
+#
+# Test auto_increment warning
+#
+create table t1 (a int primary key auto_increment) engine=aria;
+insert into t1 values (1);
+update t1 set a=0 where a=1;
+check table t1;
+select * from t1;
+drop table t1;
+
 #
 # Test problem with rows that are 65517-65520 bytes long
 #