Hi Gail,
yes and no. I think the query displayed is the query referenced in the warning. But I get many thousands of messages from many concurrent threads after I activate this setting. And I am only interested in these warnings to find locations of code that has to be redesigned in a big legacy application. It is a little bit difficult to do it currently though not impossible. That is why I set "minor" priority..
Imho to write warnings for these positional parameters is a very good thing but it seems to me it is done only half way as the query referenced is not easy to locate. The warning is written even if you do not output the sql query while it references the query. I understand that collecting information that is available somewhere else to have it displayed together with this log message is against several design principles. But maybe it is possible to provide a listener interface to listen on queries hibernate creates?
Best regards,
Carsten