Bug #49478 year(2) datatype index anomalies
| Submitted: | 5 Dec 2009 23:08 | Modified: | 23 Jun 2015 14:12 |
|---|---|---|---|
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Server: Data Types | Severity: | S3 (Non-critical) |
| Version: | 5.0.89, 5.1.41, 5.1.43 | OS: | Any |
| Assigned to: | Gleb Shchepa | CPU Architecture: | Any |
| Tags: | year | ||
[5 Dec 2009 23:08]
Shane Bester
[6 Dec 2009 6:26]
Shane Bester
maybe this is a duplicate of recently fixed bug #43668 ??
[6 Dec 2009 9:39]
Sveta Smirnova
Thank you for the report. Verified as described. See also bug #40171
[24 Nov 2010 10:40]
Manyi Lu
Please retriage based on R/E evaluation. We plan create a separate worklog to solve several related bugs in this area in upcoming releases.
[25 Nov 2010 17:36]
Shane Bester
I also vote to obsolete this silly datatype.
[23 Jun 2015 14:12]
Morgan Tocker
Posted by developer: The YEAR(2) data type was deprecated in MySQL 5.6 and removed from MySQL 5.7. For this reason, I am closing this bug as "won't fix".
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.058 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.