codingapi/tx-lcn

6.0下 SQL幂等性分析

Open

#501 opened on Jul 2, 2020

View on GitHub
 (15 comments) (0 reactions) (1 assignee)Java (4,212 stars) (1,469 forks)batch import
featureshelp wanted

Description

6.0 相比之前的底层实现上做了些调整。需要依赖分析SQL来完成事务的补偿。目前框架是通过p6spy获取到了执行到的sql，也提供了connection对象，需要基于sql与connection对象获取到。真实影响到的数据。

何为真实影响到的数据？ 比如 insert into demo(id,time,name) values(1,123,now()); 中的now() 就是一个可变参数。我们需要拿到now的真实数据，以此理解，还有id的自增长问题，还有修改语句中没有id时，要获取真实影响到的数据。删除语句中真实删除掉的语句。

Contributor guide

Tech stack
javasqlspring
Domain
databasebackend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Basic Java knowledgeUnderstanding of SQLFamiliarity with distributed transactions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
This issue requires analyzing SQL statements intercepted by p6spy to obtain actual affected data for transaction compensation, such as resolving NOW() and auto increment IDs. The maintainer's comments indicate the approach involves using the captured SQL and connection object. Relevant code likely resides in the transaction logging or SQL parsing modules. Investigation should focus on understanding how to parse and re execute SQL with resolved parameters to identify real data changes.