Bug #13996 Could not fetch catalogs/schemata data. When executing SP from script tab
Submitted: 13 Oct 2005 8:46 Modified: 13 Oct 2005 9:33
Reporter: john kanakis Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.1.13 OS:Windows (XP SP1)
Assigned to: CPU Architecture:Any

[13 Oct 2005 8:46] john kanakis
Description:
Hi, 
I think that this is a very minor bug and i might being obssesive here but i like the product and trying to help so...

when i try to run a stored procedure that returns a resault set back to client i get the error "Could not fetch catalog/schemata data". On the other hand if a try a SP wich returns only a variable it executes fine.

How to repeat:

--Create Table
drop index Index_1 on sy_seq;

drop table if exists sy_seq;

create table sy_seq
(
   id                             varchar(50)                    not null,
   aa                             numeric(10,0),
   primary key (id)
)
type = InnoDB;

insert into sy_seq (id, aa) values ('se_users', 0);
insert into sy_seq (id, aa) values ('se_roles', 0);
insert into sy_seq (id, aa) values ('sy_callcenters', 0);
insert into sy_seq (id, aa) values ('sy_cars', 0);

create index Index_1 on sy_seq
(
   id
);

--Create SP
DELIMITER $$

DROP PROCEDURE IF EXISTS `test`.`syp_seq`$$
CREATE PROCEDURE `syp_seq`(IN arg_module varchar(50))
BEGIN

  UPDATE sy_seq
     SET    aa=aa+1
     WHERE  id=arg_module;

  SELECT aa
     FROM   sy_seq
     WHERE  id=arg_module;

END$$

DELIMITER ;

--execute this to raise error
call syp_seq('se_users')
[13 Oct 2005 9:33] Vasily Kishkin
I was not able to reproduce the bug on 1.1.14. Probably the bug was fixed. Please download and install new version of MySQL QB. Thanks.