是否为mysql(5.067) bug

shang_1113 2008-11-14 04:47:11
版本为5.067
一运行类似下面的procedure,mysql就自动死掉
CREATE PROCEDURE `test`(IN v_ID VARCHAR(1))
NOT DETERMINISTIC
CONTAINS SQL
SQL SECURITY DEFINER
COMMENT ''
BEGIN
declare v_id_1 varchar(10) default null;
if v_ID='1' then
set v_id_1 = 'HBR1M';
elseif v_ID='0' then
set v_id_1 = 'HBR24H';
elseif v_ID='3' then
set v_id_1 = 'HBR3M';
elseif v_ID='6' then
set v_id_1 = 'HBR6M';
elseif v_ID='a' then
set v_id_1 = 'LBR1M';
elseif v_ID='b' then
set v_id_1 = 'LBR3M';
elseif v_ID='D' then
set v_id_1 = 'PRMBEA';
elseif v_ID='C' then
set v_id_1 = 'PRMBOC';
elseif v_ID='8' then
set v_id_1 = 'PRMHKB';
elseif v_ID='f' then
set v_id_1 = 'UST10Y';
elseif v_ID='c' then
set v_id_1 = 'UST2Y';
elseif v_ID='g' then
set v_id_1 = 'UST30Y';
elseif v_ID='e' then
set v_id_1 = 'UST5Y';
end if;
select v_ID,v_id_1;
END;


也就是procedure中if elseif 过多

帮忙看看
谢谢哦
...全文
122 2 打赏 收藏 转发到动态 举报
写回复
用AI写文章
2 条回复
切换为时间正序
请发表友善的回复…
发表回复
shang_1113 2008-11-17
  • 打赏
  • 举报
回复
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x98e7d108, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81b88e5
0xacddb0
0xacef25
0x84c24a5
0x84c2afa
0x817d8b4
0x819a323
0x8208b29
0x81fdc84
0x8202f54
0x8203995
0x823f4b7
0x81d63f9
0x8307381
0x8309a12
0x830b9c3
0x830ac6d
0x830c88a
0x81d2216
Stack trace seems successful - bottom reached
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
懒得去死 2008-11-15
  • 打赏
  • 举报
回复
Tell me how your mysqld die and what your mysqld's error log's content is?

56,677

社区成员

发帖
与我相关
我的任务
社区描述
MySQL相关内容讨论专区
社区管理员
  • MySQL
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧