Closed Jiabing-cyber closed 1 year ago
所以现在该怎么办呢, 好端端的seata调用了isAfterLast, 你们这边实现之后又抛了一个异常出来, 还不解决, 说好你们支持seata的, 为什么不继续支持了呢
我其实有点好奇, 实现了这玩意, 又都抛异常, 何必呢....
所以现在该怎么办呢, 好端端的seata调用了isAfterLast, 你们这边实现之后又抛了一个异常出来, 还不解决, 说好你们支持seata的, 为什么不继续支持了呢
问题解决了吗,我也遇到这个问题了, Shardingsphere-jdbc 5.0.0 + mybatis-plus 3.3.1+seata 1.7.0
问题解决了吗,我也遇到这个问题了, Shardingsphere-jdbc 5.0.0 + mybatis-plus 3.3.1+seata 1.7.0
@SmileDYH Can you submit a new issue to report this problem? @linghengqian's comment provided a good advice, enough information helps solve the problem, rather than just providing an exception stack.
问题解决了吗,我也遇到这个问题了, Shardingsphere-jdbc 5.0.0 + mybatis-plus 3.3.1+seata 1.7.0
@SmileDYH Can you submit a new issue to report this problem? @linghengqian's comment provided a good advice, enough information helps solve the problem, rather than just providing an exception stack.
我的问题已经解决了,使用 SELECT LAST_INSERT_ID() AS ID 避免了seata getGeneratedKeys,从而避免了isAfterLast的问题
1. execption:
2. Explain