Viewing all changes in revision 3390.1.3.
- Committer: Sergey Petrunya
- Date: 2012-01-25 14:33:57 UTC
- mto: This revision was merged to the branch mainline in revision 3394.
- Revision ID: psergey@askmonty.org-20120125143357-8mdlbpurobce40w7
BUG#920255: Wrong result (extra rows) with loosescan and IN subquery
The problem was that LooseScan execution code assumed that tab->key holds
the index used for looseScan. This is only true when range or full index
scan are used. In case of ref access, the index is in tab->ref.key (and
tab->index==0 which explains how LooseScan passed tests with ref access: they
used one index)
Fixed by setting/using loosescan_key, which always the correct index#.
The problem was that LooseScan execution code assumed that tab->key holds
the index used for looseScan. This is only true when range or full index
scan are used. In case of ref access, the index is in tab->ref.key (and
tab->index==0 which explains how LooseScan passed tests with ref access: they
used one index)
Fixed by setting/using loosescan_key, which always the correct index#.
expand all
collapse all
added
removed
