The data synchronized from dm timestamp(3) type to datetime(3) is inconsistent with the previous data

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dm timestamp(3)类型同步到 datetime(3)数据同步的和之前数据不一致

| username: TI表弟

【TiDB Environment】test
【TiDB Version】tidb v5.4 dm v6.3.0

2
| username: OnTheRoad | Original post link

What tool was used for synchronization? What is 330300? Are you sure it’s not the synchronization tool’s fault?

3
| username: TI表弟 | Original post link

The synchronization tool is DM.

4
| username: Billmay表妹 | Original post link

Try to use the same version for TiDB and DM as much as possible.

5
| username: buchuitoudegou | Original post link

The datetime type and timestamp type in TiDB are not completely equivalent: 日期和时间类型 | PingCAP 文档中心

Additionally, how are you using DM to synchronize these tables? Why do the upstream and downstream tables have different field types?

6
| username: onlyacat | Original post link

Is the upstream MariaDB or MySQL?

7
| username: TI表弟 | Original post link

The order of the table columns must be exactly the same.

8
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.