Sorry for late reply. It needs some luck and time to load the reply form without timing out and then successfully submit it.
Apparently people are so focused on code examples so that only @LanX and @ysth's replies did not completely miss the question. Actually I regret having edited the original post to add the suspected code, because it distracted from the question. But when some of the most respected forum users all demand to see code, it is sometimes not easy not to cave in.
The answer turned out to be this:
First I tried to find a method to log all DBI requests.
So I found the DBI::Log module, which unfortunately turned out dysfunctional (exiting the application after logging the first USE). However, its documentation hinted at an alternative: DBI Trace.
With DBI Trace it was easy as snap to find the actual offending command and its precise location, which was a different one than originally suspected.
Thank you all!In reply to Re: Need advice how to diagnose the problem when syntax using MAX() is correct according to MySQL monitor, but errors out in DBI
by dissident
in thread [SOLVED] Need advice how to diagnose the problem when syntax using MAX() is correct according to MySQL monitor, but errors out in DBI
by dissident
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |