#At file:///home/og136792/mysql/mysql-next-mr-opt-backporting/ based on revid:epotemkin@stripped
3242 Oystein Grovlen 2010-09-14
Bug#48213 - Materialized subselect crashes if using GEOMETRY type
Removed part of comment for Item_in_subselect::setup_engine()
since it is no longer true after fix for Bug#48213.
Removed comment that is invalid after Bug#48213 was fixed.
=== modified file 'sql/item_subselect.cc'
--- a/sql/item_subselect.cc 2010-09-07 19:07:18 +0000
+++ b/sql/item_subselect.cc 2010-09-14 09:26:55 +0000
@@ -1836,12 +1836,6 @@ bool Item_in_subselect::fix_fields(THD *
of this Item's execution. The method creates a new engine for
materialized execution, and initializes the engine.
- If this initialization fails
- - either because it wasn't possible to create the needed temporary table
- and its index,
- - or because of a memory allocation error,
- then we revert back to execution via the IN=>EXISTS tranformation.
The initialization of the new engine is divided in two parts - a permanent
one that lives across prepared statements, and one that is repeated for each
Attachment: [text/bzr-bundle] firstname.lastname@example.org
|• bzr commit into mysql-next-mr-bugfixing branch (oystein.grovlen:3242)Bug#48213||Oystein Grovlen||14 Sep|