[MDEV-4697] UPDATE_TIME field for XtraDB / InnoDB Created: 2013-06-23 Updated: 2017-11-23 Resolved: 2017-11-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Fix Version/s: | 10.2.2, 10.3.0, 10.2.11, 10.3.3 |
| Type: | Task | Priority: | Major |
| Reporter: | Dotan Cohen | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | upstream | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Description |
|
This is a port of MySQL bug # 2681 [1] to MariaDB. Currently XtraDB / InnoDB does not support the UPDATE_TIME for tables in the INFORMATION_SCHEMA. Please add this support, as is the case for other popular table types such as MyISAM. Thank you. [1] http://bugs.mysql.com/bug.php?id=2681 |
| Comments |
| Comment by Maciej Holyszko [ 2016-03-17 ] |
|
This has been fixed in MySQL 5.7.2 already (and 5.7.8 for partitioned tables). Please implement a fix in MariaDB! |
| Comment by Milan Orszagh [ 2016-03-17 ] |
|
Would be nice to have |
| Comment by Steve Fatula [ 2017-01-15 ] |
|
Well, you are referring likely to bug 14374 in mysql also. True, it is in 5.7.2, but, not persistent across server restarts. That would be WL6917 in MySQL, which is not done yet. Would like for this to be implemented in Mariadb for innodb for sure! Very very useful, for example, to find tables that were created say to solve some issue or look for something, test, whatever, but never dropped. If the last access date is years old, that's a hint! |
| Comment by Marko Mäkelä [ 2017-11-23 ] |
|
MariaDB 10.2.2 imported the InnoDB of MySQL 5.7.9. WL#6658 introduced a non-persistent update_time in MySQL 5.7.2. The tests innodb.update_time and innodb.update_time_wl6658 were missing. I imported and adjusted them for MariaDB 10.2. |