apache / apache/incubator-seata
Data too long for column table_name?
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
{
"code": "S0001",
"engDesc": null,
"chnDesc": null,
"detail": "供应商操作失败:{0}",
"content": "错误描述:供应商操作失败:{0}\n### Error updating database. Cause: java.sql.SQLException: io.seata.core.exception.RmTransactionException: Response[ TransactionException[branch register request failed. xid=10.18.51.187:8091:115140992675065856, msg=Data truncation: Data too long for column table_name at row 1] ]\n### The error may exist in class path resource [com/zy/supplier/downsource/impl/mapper/SupInfoProductDomainMtpcatalevelMapper.xml]\n### The error may involve defaultParameterMap\n### The error occurred while setting parameters\n### SQL: insert into sup_info_product_domain_mtpcatalevel ( global_supplier_id, catalog_level_id, catalog_level, version, status ) values( ?, ?, ?, ?, ? )\n### Cause: java.sql.SQLException: io.seata.core.exception.RmTransactionException: Response[ TransactionException[branch register request failed. xid=10.18.51.187:8091:115140992675065856, msg=Data truncation: Data too long for column table_name at row 1] ]\n; uncategorized SQLException; SQL state [null]; error code [0]; io.seata.core.exception.RmTransactionException: Response[ TransactionException[branch register request failed. xid=10.18.51.187:8091:115140992675065856, msg=Data truncation: Data too long for column table_name at row 1] ]; nested exception is java.sql.SQLException: io.seata.core.exception.RmTransactionException: Response[ TransactionException[branch register request failed. xid=10.18.51.187:8091:115140992675065856, msg=Data truncation: Data too long for column table_name at row 1] ] [98]"
}
Contributor guide
Research direction
Start by inspecting the SQL insert reported for com/zy/supplier/downsource/impl/mapper/SupInfoProductDomainMtpcatalevelMapper.xml and trace the Seata branch-registration error around the table_name truncation. Reproduce the failing insert against the project’s database setup; done means identifying and validating a resolution for the reported data-length failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100