Skip the SQL parsing step.
Check Ahead
-
[x] I have searched the issues of this repository and believe that this is not a duplicate.
-
[ ] I am willing to try to implement this feature myself.
Why you need it?
In an inter-service invocation scenario, an API represents a large global transaction that includes both query and update operations. The query does not need to go through SQL parsing, as parsing would lead to errors and impact performance.
How it could be?
No response
Other related information
When entering a Seata global transaction, the SQL parsing process can be intercepted, allowing selective skipping of the SQL parsing logic without affecting the rollback and commit operations of the global transaction.
Which version of Seata are you using? In non-global transactions, SQL parsing and similar operations won't be performed.