diff options
| author | unknown <mhansson/martin@linux-st28.site> | 2007-08-15 09:23:44 +0200 |
|---|---|---|
| committer | unknown <mhansson/martin@linux-st28.site> | 2007-08-15 09:23:44 +0200 |
| commit | 01f8130aa68392d14f36cc17c01e1b349bf844f5 (patch) | |
| tree | 2d9eb6b63a9f0e51771e9422008f51c07409e227 /mysql-test/include/mix1.inc | |
| parent | 1f83b351818fca51a14bc34a224c4a80e14c9476 (diff) | |
| download | mariadb-git-01f8130aa68392d14f36cc17c01e1b349bf844f5.tar.gz | |
bug#28570: handler::index_read() is called with different find_flag when
ORDER BY is used
The range analysis module did not correctly signal to the
handler that a range represents a ref (EQ_RANGE flag). This causes
non-range queries like
SELECT ... FROM ... WHERE keypart_1=const, ..., keypart_n=const
ORDER BY ... FOR UPDATE
to wait for a lock unneccesarily if another running transaction uses
SELECT ... FOR UPDATE on the same table.
Fixed by setting EQ_RANGE for all range accesses that represent
an equality predicate.
mysql-test/r/innodb_mysql.result:
bug#28570: Test Result
mysql-test/t/innodb_mysql.test:
bug#28570: Test Case
sql/handler.cc:
bug#28570: Updated comment
sql/opt_range.cc:
bug#28570: Removed the criterion that key has to be unique (HA_NOSAME) in
order for the EQ_RANGE flag to be set. It is sufficient that the range
represent a ref access.
Diffstat (limited to 'mysql-test/include/mix1.inc')
0 files changed, 0 insertions, 0 deletions