Skip to main content
Solved

Logs without the full SQL statement run


juanmahere
Supporter
Forum|alt.badge.img+11

Hi,
When launching a workbench using mostly SQLExecutors, with long sql statements, I can only see the first few lines for those statements on the Log file, for each SQLExecutor, but not the full SQL statement.

Is this something that cannot be modified?
I’d like to have all SQL lines that have been through the process.

log file
workbench

Thanks,

Juanma

Best answer by takashi

Hi ​@juanmahere ,

I don't think there is a way to modify the behavior on logging SQL statement in SQLExecutor.

However, Logger transformer will log full text for every feature attribute value, so it could be a workaround if you insert an AttributeManager (or an AttributeCreator) to create a new attribute which stores the full SQL script, add a Logger, then set the attribute to the SQL Statement parameter in the SQLExecutor.

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

takashi
Influencer
  • Best Answer
  • May 7, 2025

Hi ​@juanmahere ,

I don't think there is a way to modify the behavior on logging SQL statement in SQLExecutor.

However, Logger transformer will log full text for every feature attribute value, so it could be a workaround if you insert an AttributeManager (or an AttributeCreator) to create a new attribute which stores the full SQL script, add a Logger, then set the attribute to the SQL Statement parameter in the SQLExecutor.


nielsgerrits
VIP
Forum|alt.badge.img+54

.


juanmahere
Supporter
Forum|alt.badge.img+11
  • Author
  • Supporter
  • May 7, 2025
takashi wrote:

Hi ​@juanmahere ,

I don't think there is a way to modify the behavior on logging SQL statement in SQLExecutor.

However, Logger transformer will log full text for every feature attribute value, so it could be a workaround if you insert an AttributeManager (or an AttributeCreator) to create a new attribute which stores the full SQL script, add a Logger, then set the attribute to the SQL Statement parameter in the SQLExecutor.

Works fine using Logger here. I can see now the full SQL statement. Thanks for the tip ​@takashi 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings