File: galera_zero_length_column.test

package info (click to toggle)
mariadb-10.5 1%3A10.5.23-0%2Bdeb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 712,240 kB
  • sloc: ansic: 2,158,658; cpp: 1,843,101; asm: 297,745; perl: 59,967; sh: 53,869; pascal: 38,348; java: 33,919; yacc: 19,639; python: 11,119; xml: 10,126; sql: 10,027; ruby: 8,544; makefile: 6,343; cs: 2,866; lex: 1,205; javascript: 1,037; objc: 80; tcl: 73; awk: 46; php: 22; sed: 16
file content (41 lines) | stat: -rw-r--r-- 997 bytes parent folder | download | duplicates (7) 
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
29
30
31
32
33
34
35
36
37
38
39
40
41
 
#
# Test columns with size zero. This is known to have tripped other storage engines.
# Keys are not allowed on such columns
#

--source include/galera_cluster.inc
--source include/have_innodb.inc

--connection node_1
CREATE TABLE t1 (f1 INTEGER PRIMARY KEY , f2 VARCHAR(0)) ENGINE=InnoDB;
CREATE TABLE t2 (f1 VARCHAR(0)) ENGINE=InnoDB;


INSERT INTO t1 VALUES (1, NULL);
INSERT INTO t1 VALUES (2, '');

INSERT INTO t2 VALUES (NULL);
INSERT INTO t2 VALUES ('');

--connection node_2
SELECT COUNT(*) = 2 FROM t1;
SELECT f2 IS NULL FROM t1 WHERE f1 = 1;
SELECT f2 = '' FROM t1 WHERE f1 = 2;

SELECT COUNT(*) = 2 FROM t2;
SELECT f1 IS NULL FROM t2 WHERE f1 IS NULL;
SELECT f1 = '' FROM t2 WHERE f1 IS NOT NULL;

UPDATE t1 SET f2 = '' WHERE f1 = 1;
UPDATE t1 SET f2 = NULL WHERE f1 = 2;

UPDATE t2 SET f1 = '' WHERE f1 IS NULL;

--connection node_1
SELECT f2 = '' FROM t1 WHERE f1 = 1;
SELECT f2 IS NULL FROM t1 WHERE f1 = 2;

SELECT COUNT(*) = 2 FROM t2 WHERE f1 = '';

DROP TABLE t1;
DROP TABLE t2;