I discovered a very strange mysql behavior. Selecting below returns 0:
SELECT CONVERT('a' USING BINARY) REGEXP '[\x61]'
However, a semantically identical select below returns 1:
SELECT CONVERT('a' USING BINARY) REGEXP '[\x61-\x61]'
Do you know what is going on here? I tested this in mysql 5.0.0.3031 and 4.1.22
I need hexadecimal characters to create a regular expression that matches when a binary string is encoded in utf8. The perl version of such regexp can be found on the w3c site . It looks like this:
$field =~ m/\A( [\x09\x0A\x0D\x20-\x7E] # ASCII | [\xC2-\xDF][\x80-\xBF] # non-overlong 2-byte | \xE0[\xA0-\xBF][\x80-\xBF] # excluding overlongs | [\xE1-\xEC\xEE\xEF][\x80-\xBF]{2} # straight 3-byte | \xED[\x80-\x9F][\x80-\xBF] # excluding surrogates | \xF0[\x90-\xBF][\x80-\xBF]{2} # planes 1-3 | [\xF1-\xF3][\x80-\xBF]{3} # planes 4-15 | \xF4[\x80-\x8F][\x80-\xBF]{2} # plane 16 )*\z/x;
source share