dongyun-coder opened a new issue, #35531:
URL: https://github.com/apache/shardingsphere/issues/35531
### Which version of ShardingSphere did you use?
5.5.3-SNAPSHOT
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
Binlog parser should correctly handle datetime(4) columns with special value
'0000-00-00 00:00:00.0000'
### Actual behavior
in aws rds 8.0.32, the following table is allowed
CREATE TABLE `reproduce_datetime_parse_error`
(
`id` bigint NOT NULL AUTO_INCREMENT,
`updated` datetime(4) NOT NULL DEFAULT '0000-00-00 00:00:00.0000',
PRIMARY KEY (`id`)
) ENGINE = InnoDB;
insert into reproduce_datetime_parse_error values ();
**Binlog parser not read all bytes of column datetime(4), which should 7
bytes, but only read 5 bytes ,lost fractional seconds**
**When the parsing error occurs, the binlog client becomes corrupted**
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
[email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
