autocommit=1 not resetting session->server_status properly when committing ongoing txn

Bug #695201 reported by Stewart Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Low
Stewart Smith
7.0
Fix Released
Low
Stewart Smith

Bug Description

from delete.test:

SET AUTOCOMMIT=0;
DELETE from t1;
SET AUTOCOMMIT=1;
drop table t1;

#
# Test of delete when the delete will cause a node to disappear and reappear
# (This assumes a block size of 1024)
#

create table t1 (
        a bigint not null,
        b bigint not null default 0,
        c bigint not null default 0,
        d bigint not null default 0,
        e bigint not null default 0,
        f bigint not null default 0,
        g bigint not null default 0,
        h bigint not null default 0,
        i bigint not null default 0,
        j bigint not null default 0,
        primary key (a,b,c,d,e,f,g,h,i,j));

with this in the create table path:
 if (session->inTransaction())
    {
      my_error(ER_TRANSACTIONAL_DDL_NOT_SUPPORTED, MYF(0));
      return true;
    }

throws an error when it shouldn't. (only create table has been modifide)

Related branches

Stewart Smith (stewart)
Changed in drizzle:
assignee: nobody → Stewart Smith (stewart)
Stewart Smith (stewart)
Changed in drizzle:
status: New → In Progress
Stewart Smith (stewart)
summary: - drop table implicit commit leaves inTransaction as true
+ autocommit=1 not resetting session->server_status properly when
+ committing ongoing txn
Changed in drizzle:
importance: Undecided → Low
milestone: none → 2011-01-03
Stewart Smith (stewart)
Changed in drizzle:
milestone: 2011-01-03 → 2011-01-17
Stewart Smith (stewart)
Changed in drizzle:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.