MySQL Bugs: #5258: Stored procedure modified date is 0000-00-00

Bug #5258	Stored procedure modified date is 0000-00-00
Submitted:	27 Aug 2004 16:17	Modified:	8 Sep 2004 9:44
Reporter:	Peter Gulutzan	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0.2-alpha-debug	OS:	Linux (SuSE 8.2)
Assigned to:	Per-Erik Martin	CPU Architecture:	Any

Description:
The modified column in the mysql.proc table, at create time, has '0000-00-00 00:00:00'. 
 
This is false. I did not modify the procedure or function in the year 0000. I did not modify it 
at all. Therefore the date of the modification is not applicable. The correct value is NULL. 
 

How to repeat:
Create any procedure or function. Then: 
 
SELECT * FROM mysql.proc;

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Additional info:

show create table mysql.proc;
CREATE TABLE `proc` (
...
 `modified` timestamp NOT NULL default '0000-00-00 00:00:00',

You're right, it's documented so it's not a bug, but after further correspondence I believe 
that we can agree that `modified` (possibly renamed as `last_altered`) should initially have 
the same date as `created`. So it's something which should be fixed.

It's a design flaw and should be fixed.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html