File: binlog_mysqlbinlog_source_gipk_info.result

package info (click to toggle)
mysql-8.0 8.0.43-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,273,924 kB
  • sloc: cpp: 4,684,605; ansic: 412,450; pascal: 108,398; java: 83,641; perl: 30,221; cs: 27,067; sql: 26,594; sh: 24,181; python: 21,816; yacc: 17,169; php: 11,522; xml: 7,388; javascript: 7,076; makefile: 2,194; lex: 1,075; awk: 670; asm: 520; objc: 183; ruby: 97; lisp: 86
file content (33 lines) | stat: -rw-r--r-- 2,049 bytes parent folder | download
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

##################################################
# 1. Check the output of mysqlbinlog when the input file is a log
#    from an old version server where GIPKs are not supported
#    No info about GIPK should be present
include/assert_grep.inc [Check the output contains no information GIPK]
include/assert_grep.inc [Check the output contains no information GIPK]

##################################################
# 2. Check the output of mysqlbinlog when the input files are logs
#    created in a server version that supports GIPKs
#    Info about GIPKs should be present
include/assert_grep.inc [Check the output contains information about t1 not containing a GIPK]
include/assert_grep.inc [Check the output contains information about t2 containing a GIPK]

##################################################
# 3. Check a binlog file containing the 2 tables above, but now with --print-table-metadata
#    Even with binlog_row_metadata = minimal, data about the GIPK columns should be present
include/assert_grep.inc [Check the output contains complete info about the GIPK column on t2]
include/assert_grep.inc [Check the output contains info about the GIPK being a PK on t2]
include/assert_grep.inc [Info about the column really_unique_column_name on t2 is only mentioned once on CREATE]
include/assert_grep.inc [Check the output contains no info about c1 being a PK on t1]

##################################################
# 4. Check an equivalent binlog file but generated with binlog_row_metadata = full
#    With --print-table-metadata the info should still be the same for GIPKs
include/assert_grep.inc [Check the output contains complete info about the GIPK column on t2]
include/assert_grep.inc [Check the output contains info about the GIPK being a PK on t2]
include/assert_grep.inc [Info about the column really_unique_column_name on t2 is mentioned on CREATE and in the table map]
include/assert_grep.inc [Check the output contains info about c1 being a PK on t1]

##################################################
# 5. Cleanup