File: rr_c_count_not_zero.test

package info (click to toggle)
mariadb 1%3A11.8.2-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, trixie
  • size: 765,428 kB
  • sloc: ansic: 2,382,827; cpp: 1,803,532; asm: 378,315; perl: 63,176; sh: 46,496; pascal: 40,776; java: 39,363; yacc: 20,428; python: 19,506; sql: 17,864; xml: 12,463; ruby: 8,544; makefile: 6,059; cs: 5,855; ada: 1,700; lex: 1,193; javascript: 1,039; objc: 80; tcl: 73; awk: 46; php: 22
file content (28 lines) | stat: -rw-r--r-- 1,044 bytes parent folder | download | duplicates (19) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
 
################################################################################
#
# Verify that  SELECT COUNT(*) FROM t1 is never 0.
# This should hold because we take care not to delete all rows from that table.
#
# There have been bugs in the past where this query sporadically has returned 
# 0 for non-empty tables.
#
################################################################################

SET autocommit = 0;
START TRANSACTION;
--echo *** Running query: SELECT COUNT(*) FROM t1
let $count= `SELECT COUNT(*) FROM t1`;
if (!$count)
{
    # count was zero (0)
    --echo FAIL! SELECT COUNT(*) returned 0 - this should neven happen.
}

# Check that the count of rows with pk divisible by 5 is constant.
# This should hold because
#  a) We do not delete rows with pk MOD 5 = 0
#  b) We cannot insert new pk's below the initial auto_increment counter (see init test).
SELECT COUNT(*) FROM t1 WHERE `pk` MOD 5 = 0 AND `pk` BETWEEN 1 AND 1000;
--sleep 1
SELECT COUNT(*) FROM t1 WHERE `pk` MOD 5 = 0 AND `pk` BETWEEN 1 AND 1000;
COMMIT;