mariadb/mysql-test/suite/versioning/common_finish.inc

--disable_query_log
--disable_warnings
drop procedure if exists verify_trt;
drop procedure if exists verify_trt_dummy;
drop function if exists current_row;
drop function if exists check_row;
drop function if exists current_row_ts;
drop function if exists check_row_ts;
--enable_warnings
--enable_query_log
Tests: removed common.inc from results 2017-12-03 21:06:24 +01:00			`--disable_query_log`
Merge branch '10.2' into 10.3 2019-09-02 13:06:56 +02:00			`--disable_warnings`
			`drop procedure if exists verify_trt;`
			`drop procedure if exists verify_trt_dummy;`
			`drop function if exists current_row;`
			`drop function if exists check_row;`
MDEV-23644 Assertion on evaluating foreign referential action for self-reference in system versioned table First part of the fix (row0mysql.cc) addresses external columns when adding history row on referential action. The full data must be retrieved before the row is inserted. Second part of the fix (the rest) avoids duplicate primary key error between the history row generated on referential action and the history row generated by SQL command. Both command and referential action can happen on same table since foreign key can be self-reference (parent and child tables are same). Moreover, the self-reference can refer multiple rows when the key is non-unique. In such case history is generated by referential action occured on first row but processed all rows by a matched key. The second round is when the next row is processed by a command but history already exists. In such case we check TRX_ID of existing history row and if it is the same we assume the above situation and skip adding one more history row or failing the command. 2020-12-22 01:33:53 +01:00			`drop function if exists current_row_ts;`
			`drop function if exists check_row_ts;`
Merge branch '10.2' into 10.3 2019-09-02 13:06:56 +02:00			`--enable_warnings`
Tests: removed common.inc from results 2017-12-03 21:06:24 +01:00			`--enable_query_log`