MySQL Forums
Forum List  »  Stored Procedures

Re: Slow stored procedure call
Posted by: Bill Gladstone
Date: August 19, 2013 10:24AM

Table scans weren't occurring, but there was definitely a problem with the character set and collation of the HashedUrl column. Changing the column from CHAR(32) to BINARY(16) and using UNHEX() to convert the MD5 hash from a character string to binary fixed the problem for me.

If anyone else runs into this, the "Encryption and Compression Functions" topic at describes how to efficiently store and index hashed values.

Many thanks for the solution, Rick.

-- Bill

Edited 1 time(s). Last edit at 08/19/2013 10:25AM by Bill Gladstone.

Options: ReplyQuote

Written By
July 30, 2013 07:48PM
August 01, 2013 10:24PM
Re: Slow stored procedure call
August 19, 2013 10:24AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.