Originally created by: marty.ko...@gmail.com
What exact steps will reproduce the problem?
1. Create a stored routine
2. Edit a stored routine
3.
What was the expected output?
I expected the creation date (of the stored procedure) to keep it's
original value
What happened instead?
The creation date gets the value of the updated date. this is because the
procedure is dropped and then re-created. it would be nice though if the
Created date could be preserved. Sometimes this is valuable information
Suggested fix (optional)?
Update the creation-date in the information_schema table with the original
value (before editing), so the creation date is (sort of) preserved
Version used?
HeidiSQL revision: 2353
MySQL Server version: 5.0.51
Operating system: Windows XP
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
A limitation in MySQL, see http://dev.mysql.com/doc/refman/5.1/en/alter-procedure.html
"... you cannot change the parameters or body of a stored procedure using this
statement; to make such changes, you must drop and re-create the procedure using DROP
PROCEDURE and CREATE PROCEDURE"
Recreation of course resets the creation date of the routine. That's ugly but not
solvable in HeidiSQL.
Status: Upstream
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
There is already a feature request on mysql.com : http://bugs.mysql.com/bug.php?id=9588