diff options
| author | Igor Babaev <igor@askmonty.org> | 2021-01-25 15:21:52 -0800 |
|---|---|---|
| committer | Igor Babaev <igor@askmonty.org> | 2021-01-26 18:22:39 -0800 |
| commit | bdae8bb6fdb7e9c7875f9a3fff02eadadea50dab (patch) | |
| tree | a2199d936cb66ed3e88901435a9dfbea5fa03c9d /storage/mroonga/lib/mrn_lock.hpp | |
| parent | 21809f9a450df1bc44cef36377f96b516ac4a9ae (diff) | |
| download | mariadb-git-bdae8bb6fdb7e9c7875f9a3fff02eadadea50dab.tar.gz | |
MDEV-24675 Server crash when table value constructor uses a subselect
This patch actually fixes the bug MDEV-24675 and the bug MDEV-24618:
Assertion failure when TVC uses a row in the context expecting scalar value
The cause of these bugs is the same wrong call of the function that fixes
value expressions in the value list of a table value constructor.
The assertion failure happened when an expression in the value list is of
the row type. In this case an error message was expected, but it was not
issued because the function fix_fields_if_needed() was called for to
check fields of value expressions in a TVC instead of the function
fix_fields_if_needed_for_scalar() that would also check that the value
expressions are are of a scalar type.
The first bug happened when a table value expression used an expression
returned by single-row subselect. In this case the call of the
fix_fields_if_needed_for_scalar virtual function must be provided with
and address to which the single-row subselect has to be attached.
Test cases were added for each of the bugs.
Approved by Oleksandr Byelkin <sanja@mariadb.com>
Diffstat (limited to 'storage/mroonga/lib/mrn_lock.hpp')
0 files changed, 0 insertions, 0 deletions