[
https://issues.apache.org/jira/browse/OFBIZ-12837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744826#comment-17744826
]
Paul Foxworthy edited comment on OFBIZ-12837 at 7/22/23 7:29 AM:
-----------------------------------------------------------------
Committed to trunk in 404cb9fd0260778c801f6b7edaf7d810e4324fec
Committed to release22.01 in 4ba4b965994ce39a0b64e08c40940a00bc5ff2c0
Problem was introduced after v18.12, no need for a fix there
was (Author: paul_foxworthy):
Yes, I'll commit
> Log SQL statement in exceptions in EntitySQLProcessor
> -----------------------------------------------------
>
> Key: OFBIZ-12837
> URL: https://issues.apache.org/jira/browse/OFBIZ-12837
> Project: OFBiz
> Issue Type: Bug
> Components: framework/entity
> Reporter: Paul Foxworthy
> Assignee: Paul Foxworthy
> Priority: Minor
> Attachments:
> OFBIZ-12837_log_sql_statement_in_exceptions_in_EntitySQLProcessor-1.patch,
> OFBIZ-12837_log_sql_statement_in_exceptions_in_EntitySQLProcessor.patch
>
>
> The combination of OFBIZ-11926 and OFBIZ-12386 means the field
>
> {{SQLProcessor.sql}}
>
> is never set, but it is assumed to be there in several catches - see the
> patch.
>
> If an exception occurs, you'll get a "null" and not the statement that caused
> the exception.
>
> I had a bit to say about how the problem arose in a comment on OFBIZ-11926.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
