[MDEV-6945] SET STATEMENT autocommit=... has no effect and causes warnings in the error log Created: 2014-10-25 Updated: 2015-02-02 Resolved: 2014-10-29 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Admin statements |
| Affects Version/s: | N/A |
| Fix Version/s: | 10.1.2 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Oleksandr Byelkin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Note: I couldn't find a test so I don't know whether it should work. If not, probably the attempt should cause a warning (not the one described below, but a normal one, "not supported" or something).
The part SET STATEMENT autocommit=1 FOR .. also causes warnings in the error log:
It's all the same in Percona server. |
| Comments |
| Comment by Oleksandr Byelkin [ 2014-10-26 ] |
|
adding COMMIT after SET STATEMENT does not fix situation... it is strange. |
| Comment by Oleksandr Byelkin [ 2014-10-27 ] |
|
The problem is that we return old value of autocommit before code in mysql_execute_commend() which decides if we should close transaction... |
| Comment by Oleksandr Byelkin [ 2014-10-27 ] |
|
Moving returning to old variables 'down' is problematic due to freeing resources... |
| Comment by Oleksandr Byelkin [ 2014-10-29 ] |
|
The variable is prohibited in SET STATEMENT for now. |