+13Hi,
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.
Thanks,
Juanma
Best answer by takashi
Hi
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.
Hi
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.
+13Hi
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
