FYI,

4.1.16 appears not to be using prefixes of compound indexes when doing
updates.  Reverting to 4.1.15, or adding an index consisting of only
the desired field, restores reasonable behavior.

I have added feedback to a possibly-related bug,
<http://bugs.mysql.com/bug.php?id=15935>, but wanted to send a message
on the list in case someone is having trouble with 4.1.16 and doesn't
know why, or is thinking of upgrading and might want to wait, or knows
a solution to this problem besides downgrading.

[Linux, MySQL-compiled x86_64 binary, InnoDB or MyISAM tables.]

--Pete

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to