seata解决脏读 select语句+for update + @GlobalLock + @Transactional, 并且同时使用sharding-jdbc4版本,该版本和高版都不支持 savePoint技术,但是@GlobalLock采用了savePoint技术，导致整合失败

这可咋办

Start by reproducing the combination of SELECT FOR UPDATE, @GlobalLock, @Transactional, and sharding-jdbc4 described in the issue. Trace how @GlobalLock uses savepoints and compare that with sharding-jdbc4's stated lack of savepoint support; done means the integration works without failure or the incompatibility is clearly documented.

Written by the indexing model from the issue text.