transactions - Rollback not working in MySQL 5.0.96 -


rollback not working in mysql

the user table engine innodb.

this have.

mysql> show variables 'have_innodb'; +---------------+-------+ | variable_name | value | +---------------+-------+ | have_innodb   | yes   | +---------------+-------+   mysql> show variables "%version%"; +-------------------------+------------------------------+ | variable_name           | value                        | +-------------------------+------------------------------+ | protocol_version        | 10                           | | version                 | 5.0.96-log                   | | version_comment         | mysql community server (gpl) | | version_compile_machine | x86_64                       | | version_compile_os      | unknown-linux-gnu            | +-------------------------+------------------------------+   create table `k_customer` (   `id` int(11) not null auto_increment,   ..     `updated` timestamp null default current_timestamp on update current_timestamp,   primary key  (`id`),   unique key `index_id` (`id`) ) engine=innodb auto_increment=93 default charset=utf8;

this try test:

start transaction;   insert `k_customer` values ('91', .. , '2013-04-21 21:48:46'); rollback;

and inserts record...

i tried

alter table `k_customer` engine = innodb;

but not help.

there no such problem on local db

mysql> show variables "%version%"; +-------------------------+------------------------------+ | variable_name           | value                        | +-------------------------+------------------------------+ | innodb_version          | 1.1.8                        | | protocol_version        | 10                           | | slave_type_conversions  |                              | | version                 | 5.5.24-log                   | | version_comment         | mysql community server (gpl) | | version_compile_machine | x86                          | | version_compile_os      | win64                        | +-------------------------+------------------------------+

i know there heaps of questions this. read many of them , post here data might relevant issue because misuse of may cause exact problem have. other answered question not me.


Comments

Post a Comment

Popular posts from this blog

Java sticky instances of class com.mysql.jdbc.Field aggregating -

i noticed (via jmap+jhat) app leaking storing many instances com.mysql.jdbc.field  class - double checked code make sure closing preparedstatements, find few missing didn't change outcome. - preparedstatement created , closed right away - several others created @ start , reused many times - using org.apache.tomcat.jdbc.pool.datasource connection pool what can cause type of behavior? are closing of preparedstatements / result sets using: preparedstatement stmt (possible assignment here); try { // work prepared statement resultset rs; try { while (rs.next()) ... // process results } { rs.close(); } } { stmt.close(); } so guarantee result sets closed when finished (regardless of exceptions) , statements closed (regardless of exceptions)? there other ways write that, idea same. if you're doing of properly, unless have many references it's taking inordinate amount of memory, it's ok , nothing needs done it.
Read more