On 25/09/2014 23:17, Shamim Shahriar wrote:

On 25/09/2014 19:14, Rimas Kudelis wrote:

Hi folks,
this would make sense. It would explain why regardless of the number
of closing braces you'd add, the condition fails.
Just to make sure that it's not just logs where the cropping occurs,
could you find a working condition and break it by introducing some
random whitespace or other useless chars in it?

Rimas, you wanted to see a length change factor, sorry I forgot to add this bit.

With
SA_Query = select users.sa_tag * 10 from users,domains ;

the error is
22:48:49 16989 failed to expand: ${lookup mysql{select users.sa_tag * 10 from users,domains ;}{$value}f

and with
SA_Query = select users.sa_tag * 10 from users,domains
(the line literally ends at the last s)

the error is
23:06:44 19963 failed to expand: ${lookup mysql{select users.sa_tag * 10 from users,domains}{$value}fai

putting them together, I'd say they do exhibit the symptoms of length issues

23:06:44 19963 failed to expand: ${lookup mysql{select users.sa_tag * 10 from users,domains}{$value}fai
22:48:49 16989 failed to expand: ${lookup mysql{select users.sa_tag * 10 from users,domains ;}{$value}f

And then, I changed it to something even shorter
SA_Query = select users.sa_tag from users,domains

and that expanded to
23:30:13 23669 failed to expand: ${if or { { <{$spam_score_int}{1} } { <{$spam_score_int}{${lookup mysql{select users.sa_tag from users,domains}{$value}fail}} }
23:30:13 23669�� error message: invalid integer "2

which indicates that the query part of it did work out (even though the result did not have any meaning, but the 'select' part worked) when it was shortened to an impractical (IMHO) length. I cannot think of any practical/functional query that I can fit in this short length -- but then again, I am not a sql expert, maybe someone with a better knowledge can fit that long query into this smaller space -- but I surely cannot.

Does is help in what you are looking for?

I need to turn in now. All the best
Shah