jdbc:TAOS-WS通过mybatisplus批量插入报错,换RS包正常
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 25.1k
- Forks
- 5k
- Avg merge
- 4d 59m
- Merged PRs (30d)
- 7
Description
Bug Description
按照官网的批量插入super表的方式:
1.
报错: single table allowed in one stmt
- 官网文档第二种方式:
报错: Illegal number of columns
这是我的mapper(表名不同,sql语句差不多):
To Reproduce
Steps to reproduce the behavior:
目前测试只要使用jdbc:TAOS-WS, values后面跟多条记录一定报错,单条可以插入
修改为jdbc:TAOS-RS 连接后正常, values后可通过'foreach'同时插入多条
版本为:
- TDengine Version [3.4.1.13]
- JDBC Version [3.8.3]
Expected Behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
- TDengine Version [3.4.1.13]
- JDBC Version [3.8.3]
Additional Context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the MyBatis-Plus mapper batch insert with the JDBC TAOS-WS connection, using the documented super-table approaches and the foreach values case described in the issue. Compare the failures with the same inserts over JDBC TAOS-RS; done means multi-row insertion works through TAOS-WS without the single-table or column-count errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100