summaryrefslogtreecommitdiff
path: root/mysql-test/suite
diff options
context:
space:
mode:
authorAditya A <aditya.a@oracle.com>2018-10-10 18:05:02 +0530
committerMarko Mäkelä <marko.makela@mariadb.com>2019-01-23 19:46:35 +0200
commitaa8a31dadd21ada93bc3c739de866c78614e746a (patch)
tree381c15b4e89a47c0c3a950168ad775bde11a52ad /mysql-test/suite
parente32305e50553f3cddf29f13005910e22cc90bcaf (diff)
downloadmariadb-git-aa8a31dadd21ada93bc3c739de866c78614e746a.tar.gz
Bug #22990029 GCOLS: INCORRECT BEHAVIOR AFTER DATA INSERTED WITH IGNORE KEYWORD
PROBLEM ------- 1. We are inserting a base column entry which causes an invalid value by the function provided to generate virtual column,but we go ahead and insert this due to ignore keyword. 2. We then delete this record, making this record delete marked in innodb. If we try to insert another record with the same pk as the deleted record and if the rec is not purged ,then we try to undelete mark this record and try to build a update vector with previous and updated value and while calculating the value of virtual column we get error from server that we cannot calculate this from base column. Innodb assumes that innobase_get_computed_value() Should always return a valid value for the base column present in the row. The failure of this call was not handled ,so we were crashing. FIX
Diffstat (limited to 'mysql-test/suite')
0 files changed, 0 insertions, 0 deletions