Bug #22982 | not able to restore stored procedures | ||
---|---|---|---|
Submitted: | 4 Oct 2006 14:05 | Modified: | 5 Nov 2006 7:13 |
Reporter: | suman mehta | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.0.22 | OS: | |
Assigned to: | CPU Architecture: | Any |
[4 Oct 2006 14:05]
suman mehta
[4 Oct 2006 14:06]
suman mehta
sample file having a stored procedure
Attachment: aa 20061004 1933.sql (text/plain), 1.25 KiB.
[4 Oct 2006 14:06]
suman mehta
one more
Attachment: suman (text/plain), 22.45 KiB.
[4 Oct 2006 14:10]
suman mehta
changing severity
[4 Oct 2006 15:56]
Valeriy Kravchuk
Please, try to repeat with a newer version of MySQL server, 5.0.24a, and use mysqldump/mysql command line tools to dump and restore, not MySQL Adminsitrator. Inform about the results.
[5 Oct 2006 5:50]
suman mehta
Thanks.. I used mysqldump and mysql commands to dump and restore backup. with -R option I am able to restore stored procedures but it throws error and one of the stored procedures is not restored. ERROR 1074 (42000) at line 633: Column length too big for column '' (max = 21845 ); use BLOB or TEXT instead
[5 Oct 2006 7:13]
Valeriy Kravchuk
Please, send the exact statement that has that line 633 in it.
[6 Nov 2006 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".