2 Nov
2014
2 Nov
'14
8:39 a.m.
Isaac Boukris wrote:
I was faced with the same problem today (version 2.5.5).
I managed to get it working by replacing the function 'sql_escape_func' in 'rlm_sql.c' with the function 'sql_utf8_escape_func' from 'rlm_sql_log.c' file.
This seems to pass basic tests, but I am not sure what are the implications of this change.
Not much. The best thing is probably to treat the "safe-characters" string as ASCII. Then, allow any multi-byte UTF-89 character. I'll put a fix in before the next release. Alan DeKok.