Much like RemoveDuplicatesIterator, but works on the basis of a given index (or more accurately, its keypart), not an arbitrary list of grouped fields.
More...
#include <composite_iterators.h>
Much like RemoveDuplicatesIterator, but works on the basis of a given index (or more accurately, its keypart), not an arbitrary list of grouped fields.
This is only used in the non-hypergraph optimizer; the hypergraph optimizer can deal with groupings that come from e.g. sorts.
◆ RemoveDuplicatesOnIndexIterator()
◆ EndPSIBatchModeIfStarted()
void RemoveDuplicatesOnIndexIterator::EndPSIBatchModeIfStarted |
( |
| ) |
|
|
inlineoverridevirtual |
Ends performance schema batch mode, if started.
It's always safe to call this.
Iterators that have children (composite iterators) must forward the EndPSIBatchModeIfStarted() call to every iterator they could conceivably have called StartPSIBatchMode() on. This ensures that after such a call to on the root iterator, all handlers are out of batch mode.
Reimplemented from RowIterator.
◆ Init()
bool RemoveDuplicatesOnIndexIterator::Init |
( |
| ) |
|
|
overridevirtual |
Initialize or reinitialize the iterator.
You must always call Init() before trying a Read() (but Init() does not imply Read()).
You can call Init() multiple times; subsequent calls will rewind the iterator (or reposition it, depending on whether the iterator takes in e.g. a Index_lookup) and allow you to read the records anew.
Implements RowIterator.
◆ Read()
int RemoveDuplicatesOnIndexIterator::Read |
( |
| ) |
|
|
overridevirtual |
Read a single row.
The row data is not actually returned from the function; it is put in the table's (or tables', in case of a join) record buffer, ie., table->records[0].
- Return values
-
0 | OK |
-1 | End of records |
1 | Error |
Implements RowIterator.
◆ SetNullRowFlag()
void RemoveDuplicatesOnIndexIterator::SetNullRowFlag |
( |
bool |
is_null_row | ) |
|
|
inlineoverridevirtual |
Mark the current row buffer as containing a NULL row or not, so that if you read from it and the flag is true, you'll get only NULLs no matter what is actually in the buffer (typically some old leftover row).
This is used for outer joins, when an iterator hasn't produced any rows and we need to produce a NULL-complemented row. Init() or Read() won't necessarily reset this flag, so if you ever set is to true, make sure to also set it to false when needed.
Note that this can be called without Init() having been called first. For example, NestedLoopIterator can hit EOF immediately on the outer iterator, which means the inner iterator doesn't get an Init() call, but will still forward SetNullRowFlag to both inner and outer iterators.
TODO: We shouldn't need this. See the comments on AggregateIterator for a bit more discussion on abstracting out a row interface.
Implements RowIterator.
◆ StartPSIBatchMode()
void RemoveDuplicatesOnIndexIterator::StartPSIBatchMode |
( |
| ) |
|
|
inlineoverridevirtual |
Start performance schema batch mode, if supported (otherwise ignored).
PFS batch mode is a mitigation to reduce the overhead of performance schema, typically applied at the innermost table of the entire join. If you start it before scanning the table and then end it afterwards, the entire set of handler calls will be timed only once, as a group, and the costs will be distributed evenly out. This reduces timer overhead.
If you start PFS batch mode, you must also take care to end it at the end of the scan, one way or the other. Do note that this is true even if the query ends abruptly (LIMIT is reached, or an error happens). The easiest workaround for this is to simply call EndPSIBatchModeIfStarted() on the root iterator at the end of the scan. See the PFSBatchMode class for a useful helper.
The rules for starting batch and ending mode are:
- If you are an iterator with exactly one child (FilterIterator etc.), forward any StartPSIBatchMode() calls to it.
- If you drive an iterator (read rows from it using a for loop or similar), use PFSBatchMode as described above.
- If you have multiple children, ignore the call and do your own handling of batch mode as appropriate. For materialization, #2 would typically apply. For joins, it depends on the join type (e.g., NestedLoopIterator applies batch mode only when scanning the innermost table).
The upshot of this is that when scanning a single table, batch mode will typically be activated for that table (since we call StartPSIBatchMode() on the root iterator, and it will trickle all the way down to the table iterator), but for a join, the call will be ignored and the join iterator will activate batch mode by itself as needed.
Reimplemented from RowIterator.
◆ UnlockRow()
void RemoveDuplicatesOnIndexIterator::UnlockRow |
( |
| ) |
|
|
inlineoverridevirtual |
◆ m_first_row
bool RemoveDuplicatesOnIndexIterator::m_first_row |
|
private |
◆ m_key
KEY* RemoveDuplicatesOnIndexIterator::m_key |
|
private |
◆ m_key_buf
uchar* RemoveDuplicatesOnIndexIterator::m_key_buf |
|
private |
◆ m_key_len
const size_t RemoveDuplicatesOnIndexIterator::m_key_len |
|
private |
◆ m_source
◆ m_table
const TABLE* RemoveDuplicatesOnIndexIterator::m_table |
|
private |
The documentation for this class was generated from the following files: