Question

I call a procedure, it runs, and the console says “0 rows affected”. Is this normal behavior for a MySQL procedure ?

The procedures are clearly doing what they should. One procedure has 2 insert statements, another has an insert and update statement, and I’ve seen the results with my own eyes. There are indeed rows being affected.

I’m not sure that I would use that result later on, but it seems like I’d want to get an accurate response from my DB whether or not anything was updated, especially when its expected.

Thoughts ?

MySQL 5.5 if it matters, and the procedures use transactions over auto-committed statements.

CREATE DEFINER=`root`@`localhost` PROCEDURE `create_issue`(user_id SMALLINT, title varchar(255), body LONGTEXT)
BEGIN
    DECLARE MYUSERID SMALLINT;
    DECLARE EXIT HANDLER FOR SQLEXCEPTION BEGIN END;
START TRANSACTION;
    INSERT INTO tracker.issue (user_id, title, body, creation_date, last_mod_date) values (user_id, title, body, CURDATE(), CURDATE());
    UPDATE user_activity SET last_new_issue = CURDATE(), post_count = post_count + 1 WHERE user_activity.user_id = user_id;
COMMIT;
END

Edited to show the actual query. Also I’ve been searching and as best as I can tell this is a known issue over a year and a half old. So I suppose this one can be closed.

Answer 1

I guess this is a reported bug. May be a good question for MySQL mailing list/forum. http://bugs.mysql.com/bug.php?id=44854