diff options
author | Alexander Barkov <bar@mariadb.com> | 2020-05-19 13:30:42 +0400 |
---|---|---|
committer | Alexander Barkov <bar@mariadb.com> | 2020-05-19 13:34:39 +0400 |
commit | 996b9a9d0459e371d01c63584f95101f3703900b (patch) | |
tree | d3ccbfbd2b77022df01312fab43a9bd55ccb518f /sql/item.h | |
parent | 0f9bfcc323f76389eab23220d757e1cdfacb0543 (diff) | |
download | mariadb-git-996b9a9d0459e371d01c63584f95101f3703900b.tar.gz |
MDEV-22591 Debug build crashes on EXECUTE IMMEDIATE '... WHERE ?' USING IGNORE
Removing a wrong DBUG_ASSERT:
When Item_param gets "unfixed" in cleanup(), its "fixed" gets assigned
to false, while item_item keeps the value. So the assert was wrong.
Perhaps, instead of removing the assert, it was possible to reset
item_type to NO_VALUE in cleanup. But this is not very important:
it's implemented in 10.4 in a better way:
Item_param::is_fixed() always returns true and it does not need to be "unfixed".
Diffstat (limited to 'sql/item.h')
-rw-r--r-- | sql/item.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/sql/item.h b/sql/item.h index 4d861623836..6f009fe904b 100644 --- a/sql/item.h +++ b/sql/item.h @@ -3140,7 +3140,6 @@ public: enum Type type() const { - DBUG_ASSERT(fixed || state == NO_VALUE); return item_type; } |