MySQL Bugs: #105057: data type does not match at range columns partitioning

Bug #105057	data type does not match at range columns partitioning
Submitted:	28 Sep 2021 3:19	Modified:	28 Oct 2021 7:09
Reporter:	Boy Zhang	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Partitions	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
Define a range columns partition table, the part field is of the datetime type, when the part range is of the time type, it is legal, but the semantics are not clear, and even the effect of MAX_VALUE is achieved.

How to repeat:
mysql> create table t(a int, b datetime) partition by range columns(b) (partition p0 values less than('25:00:00'));

mysql> insert into t values(1, NOW());

Suggested fix:
Shouldn't this part range be supported here?

Hi,

What exactly are you expecting to happen?

The only thing that I could consider a bug here is that 

create table t(a int, b datetime) partition by range columns(b) (partition p0 values less than('25:00:00'));

did not end up with error as '25:00:00' is not a valid datetime value as b is of datetime type

Maybe you wanted to ... partition by range (TIME(b)) ... ?

kind regards

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".