I don't know how to treat is correct.
It is problem about error handling intention at mysqld.
InnoDB (this patch) is just returning error at ht->commit() at ha_commit_one_phase().
At normal InnoDB, innobase_commit() always returns 0.
So mysqld might not be prepared for retuning error from ha->commit()?
It seems just to avoid the assertion that sandwitched by
"
thd->main_da.can_overwrite_status= TRUE;
...
thd->main_da.can_overwrite_status= FALSE;
"
But I don't know whether it is correct as mysqld intention.
I don't know how to treat is correct. one_phase( ).
It is problem about error handling intention at mysqld.
InnoDB (this patch) is just returning error at ht->commit() at ha_commit_
At normal InnoDB, innobase_commit() always returns 0.
So mysqld might not be prepared for retuning error from ha->commit()?
It seems just to avoid the assertion that sandwitched by da.can_ overwrite_ status= TRUE; da.can_ overwrite_ status= FALSE;
"
thd->main_
...
thd->main_
"
But I don't know whether it is correct as mysqld intention.