File: cons_snapshot_serializable.result

package info (click to toggle)
mariadb-10.0 10.0.30-0%2Bdeb8u2
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 474,048 kB
  • ctags: 183,740
  • sloc: cpp: 1,391,728; ansic: 831,813; perl: 59,717; sh: 36,566; pascal: 32,281; yacc: 14,921; xml: 5,257; sql: 4,660; cs: 4,647; makefile: 4,555; ruby: 4,465; python: 2,292; lex: 1,427; java: 941; asm: 295; awk: 54; php: 22; sed: 16
file content (18 lines) | stat: -rw-r--r-- 579 bytes parent folder | download | duplicates (11) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
 
DROP TABLE IF EXISTS t1;
connect  con1,localhost,root,,;
connect  con2,localhost,root,,;
connection con1;
CREATE TABLE t1 (a <INT_COLUMN>) ENGINE=<STORAGE_ENGINE> <CUSTOM_TABLE_OPTIONS>;
SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE;
START TRANSACTION WITH CONSISTENT SNAPSHOT;
connection con2;
INSERT INTO t1 (a) VALUES (1);
connection con1;
# If consistent read works on this isolation level (SERIALIZABLE), the following SELECT should not return the value we inserted (1)
SELECT a FROM t1;
a
COMMIT;
connection default;
disconnect con1;
disconnect con2;
DROP TABLE t1;