New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is there a SET AUTOCOMMIT=0 in the SQL of a database export #15802
Comments
|
Seems like a bug, thank you for reporting it ! |
|
I also can't think of a reason why this would be the intended behavior.
Thanks for reporting this!
|
|
@williamdes I am willing to work on this issue :) |
|
@kartik1000 I assigned it to you for now |
|
What should I prefer removing SET AUTO COMMIT = 0 or Adding SET AUTO COMMIT = 1? @williamdes |
|
I would suggest removing the |
|
ok @Mattie112 |
|
And just to confirm: The docs state this for 8.0, 5.7, 5.6 and 5.5 The MariaDB docks also state this:
|
Signed-off-by: William Desportes <williamdes@wdes.fr>
The first 4 lines of a database export with default settings in phpMyAdmin are:
The last 4 lines contain:
I see that the AUTOCOMMIT is disabled but never enabled. I have noticed because we imported a SQL (generated by phpMyAdmin) and in the same session also executed some INSERT statements. These rows where not visible in the database (because they where never committed).
In the MySQL docs I read this:
This states that a
SET AUTOCOMMIT = 0automatically when starting a transaction. Is there a reason why phpMyAdmin disables the autocommit and then never enables it? Is it possible to remove theSET AUTOCOMMIT=0or add aSET AUTOCOMMIT=1on the last line of the export?The text was updated successfully, but these errors were encountered: