one more problem arose for 5.5 version due to the fix. Problem is that 5.5 strnxfrm will always pad the full destination string buffer. We don't know upfront how many characters will be converted, so allocation a good destination buffer is best guess, using safe default in the fix in revision:
one more problem arose for 5.5 version due to the fix. Problem is that 5.5 strnxfrm will always pad the full destination string buffer. We don't know upfront how many characters will be converted, so allocation a good destination buffer is best guess, using safe default in the fix in revision:
http:// bazaar. launchpad. net/~codership/ codership- mysql/wsrep- 5.5/revision/ 4006