You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latter insert statement will be committed directly instead of rolling back.
The reason is, after changing user, the autocommit on the backend will be set to default true, while last_set_autocommit is still 0 which was set during the former insert query.
So in MySQL_Connection::IsAutoCommit, it is treated as mysql issue 66884 by mistake, and assumes autocommit is false, thus not changing it on the backend.
cc @MOON-CLJ
The text was updated successfully, but these errors were encountered:
test schema:
test script:
The latter insert statement will be committed directly instead of rolling back.
The reason is, after changing user, the autocommit on the backend will be set to default
true
, whilelast_set_autocommit
is still 0 which was set during the former insert query.So in
MySQL_Connection::IsAutoCommit
, it is treated as mysql issue 66884 by mistake, and assumes autocommit is false, thus not changing it on the backend.cc @MOON-CLJ
The text was updated successfully, but these errors were encountered: