2 Nov
2014
2 Nov
'14
5:40 p.m.
Arran Cudbard-Bell wrote:
I've pushed a fix to process UTF8 chars correctly for the %{escape:} and %{unescape:} xlats.
OK.
I'm guessing the decision to pass through UTF8 chars here is more a matter of convenience for the administrator than not wanting to write the code :)
O(N^2) string comparisons are bad. The problematic SQL characters are ASCII. They need to be escaped. The rest can be passed through to SQL. Alan DeKok.