Some functions are not null-preserving. For those functions updating of the maybe_null attribute is an overkill.
this value should be determined dynamically, based on statistics: uint32_t max_tables_for_exhaustive_opt= 7;
this value could be determined by some mapping of the form: depth : table_count -> [max_tables_for_exhaustive_opt..MAX_EXHAUSTIVE]
set session->lex().sql_command to SQLCOM_END here.
The following has to be changed to an 8 byte integer
Note, that create_sort_index calls test_if_skip_sort_order and may finally replace sorting with index scan if there is a LIMIT clause in the query. It's never shown in EXPLAIN!
When can we have here session->net.report_error not zero?
Would this be more suitable as a member function on the Root class?
next part may be unneeded due to this->first_block_usage counter
Make it a method of Session and align its name with the rest of reset/end/start/init methods.
Call it after we use Session for queries, not before.
how to distinguish from a JOIN?
how to distinguish from a table sequence?
Of course, this is not efficient to create a new input stream every time we call the UDF. Create a pool of TransactionLogReader objects that can be re-used.
Error message for this...
Error message for this...
Of course, this is not efficient to create a new input stream every time we call the UDF. Create a pool of TransactionLogReader objects that can be re-used.
Error message for this...
Error message for this...