Re: mysql_stmt_execute() trashing stack

[John Deal]

I could still get stack trashing even with re-preparing offending mysql_stmt_execute() statement. Converted the two methods that accessed Subscription table (see below) to use mysql_real_query() instead. This seemed to have fixed the problem with valgrind not reporting any violations.

It is strange this is only happening on one table of a multi-table database. The target table is fairly simple. The definition is below:

create table subscriptions
(
subscriptionID integer unsigned primary key auto_increment,
userID integer unsigned,
workplaceID integer unsigned,
rolesID integer unsigned,
constraint foreign key (userID) references users(userID)
on delete cascade on update cascade,
constraint foreign key (workplaceID) references workplaces(workplaceID)
on delete cascade on update cascade
constraint foreign key (rolesID) references roles(roleID) on delete cascade
on update cascade
)
engine InnoDB;

Does anybody see anything in this table definition that could cause problems with prepared statements?

Thanks!