| Bug #20075 | CREATION_TIME, LAST_UPDATE_TIME, LAST_ACCESS_TIME no updated information_schema | ||
|---|---|---|---|
| Submitted: | 25 May 2006 18:57 | Modified: | 29 May 2006 15:39 |
| Reporter: | Jonathan Miller | Email Updates: | |
| Status: | Closed | ||
| Category: | Server: Docs | Severity: | S3 (Non-critical) |
| Version: | 5.1 | OS: | Linux (Linux 32 Bit OS) |
| Assigned to: | Jon Stephens | Target Version: | |
| Triage: | D4 (Minor) | ||
[29 May 2006 7:14]
Stewart Smith
As per spec in WL1359: CREATION_TIME As reported by operating system. LAST_UPDATE_TIME As reported by operating system. LAST_ACCESS_TIME As reported by operating system. For all "as reported by operating system" columns, the value may be NULL. But if the implementor decides to report it, and the operating system supports it, that's nice. Perhaps we need to update the documentation with this (saying NDB doesn't currently put anything in these columns)? Otherwise we add extra code to NDBAPI to stat each file on each node. I've created a worklog WL3296 for this. Good introduction for a new NDB hacker.
[29 May 2006 15:39]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant product(s). Additional info: Updated I_S.FILES documentation as suggested. (Changed category to Docs.)
Description: *************************** 1. row *************************** FILE_NAME: datafile2.dat FILE_TYPE: DATAFILE TABLESPACE_NAME: ts1 LOGFILE_GROUP_NAME: lg2 LOGFILE_GROUP_NUMBER: 0 EXTENT_SIZE: 1048576 FREE_EXTENTS: 12 TOTAL_EXTENTS: 12 INITIAL_SIZE: 12582912 MAXIMUM_SIZE: 12582912 STATUS: NORMAL EXTRA: CLUSTER_NODE=2 CREATION_TIME: 0000-00-00 00:00:00 LAST_UPDATE_TIME: 0000-00-00 00:00:00 LAST_ACCESS_TIME: 0000-00-00 00:00:00 *************************** 2. row *************************** FILE_NAME: datafile2.dat FILE_TYPE: DATAFILE TABLESPACE_NAME: ts1 LOGFILE_GROUP_NAME: lg2 LOGFILE_GROUP_NUMBER: 0 EXTENT_SIZE: 1048576 FREE_EXTENTS: 12 TOTAL_EXTENTS: 12 INITIAL_SIZE: 12582912 MAXIMUM_SIZE: 12582912 STATUS: NORMAL EXTRA: CLUSTER_NODE=3 CREATION_TIME: 0000-00-00 00:00:00 LAST_UPDATE_TIME: 0000-00-00 00:00:00 LAST_ACCESS_TIME: 0000-00-00 00:00:00 *************************** 3. row *************************** mysql> use test Database changed mysql> CREATE TABLE t1 (a INT PRIMARY KEY, b CHAR(4) NOT NULL, c CHAR(4) NOT NULL, KEY(b)) TABLESPACE ts1 STORAGE DISK ENGINE = NDB; Query OK, 0 rows affected (1.16 sec) mysql> INSERT INTO t1 VALUES (1,'1','1'), (2,'2','2'), (3,'3','3'); *************************** 1. row *************************** FILE_NAME: datafile2.dat FILE_TYPE: DATAFILE TABLESPACE_NAME: ts1 LOGFILE_GROUP_NAME: lg2 LOGFILE_GROUP_NUMBER: 0 EXTENT_SIZE: 1048576 FREE_EXTENTS: 10 TOTAL_EXTENTS: 12 INITIAL_SIZE: 12582912 MAXIMUM_SIZE: 12582912 STATUS: NORMAL EXTRA: CLUSTER_NODE=2 CREATION_TIME: 0000-00-00 00:00:00 LAST_UPDATE_TIME: 0000-00-00 00:00:00 LAST_ACCESS_TIME: 0000-00-00 00:00:00 *************************** 2. row *************************** FILE_NAME: datafile2.dat FILE_TYPE: DATAFILE TABLESPACE_NAME: ts1 LOGFILE_GROUP_NAME: lg2 LOGFILE_GROUP_NUMBER: 0 EXTENT_SIZE: 1048576 FREE_EXTENTS: 10 TOTAL_EXTENTS: 12 INITIAL_SIZE: 12582912 MAXIMUM_SIZE: 12582912 STATUS: NORMAL EXTRA: CLUSTER_NODE=3 CREATION_TIME: 0000-00-00 00:00:00 LAST_UPDATE_TIME: 0000-00-00 00:00:00 LAST_ACCESS_TIME: 0000-00-00 00:00:00 *************************** 3. row *************************** How to repeat: see above Suggested fix: record dates and times