Use correct access method, found using sql-bench and comparing with other handler.
BitKeeper/deleted/.del-regression.sh~c19f771726612629: Delete: ndb/bin/regression.sh sql/ha_ndbcluster.cc: Change index flags, remove HA_WRONG_ASCII_ORDER and HA_ONLY_WHOLE_INDEX. HA_WRONG_ASCII_ORDER was used in field::optimize_range and if it was set, the index was hardly ever used. Correct check of start_key and start_key->flag != HA_READ_KEY_EXACT, ignore end-Key in suc a case Updated implementation o read_range_first Made the calculation of number of bytes par batch easier to underatsn and easier to configure. The value bytesperbatch can be made a config variable. AReduce the number of bytes sent per batch, don't overload. Increase the value returned from scan_time in order to make it clear to optimizer that scanning is the worst alternative. Always use index if available.
Showing
This diff is collapsed.
Please register or sign in to comment