-
I've added a code responsible for adding this missing index. I've verified that fix add the index and that index is used by MySQL during execution of this query.
Below is result of execution of following explain in JSON.
[ { "id": "1", "select_type": "SIMPLE", "table": "tig_ma_jids", "partitions": null, "type": "ref", "possible_keys": "tig_ma_jids_jid_index", "key": "tig_ma_jids_jid_index", "key_len": "1023", "ref": "const", "rows": "1", "filtered": 100, "Extra": "Using where" } ]
I've verified SQL schemas for version 2.0.0, but there is no need for an index on
jid
field as for MySQLjid_id
is looked up using newly introducedjid_sha1
field which already has an index.
Type |
Bug
|
Priority |
Critical
|
Assignee | |
RedmineID |
6657
|
Issue Votes (0)
Watchers (0)
It looks like there is a missing index on
tig_ma_jids
conflicted with multiplesselect
calls: