We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If one INSERT statement fails for some reason, the previously imported ones should be rolled back. Very useful.
I'm not sure if Postgres and MySQL use the same syntax and since which versions they support it. Expert advice appreciated.
The text was updated successfully, but these errors were encountered:
https://dev.mysql.com/doc/refman/5.0/en/commit.html
They both can use "begin;" and "commit;".
Sorry, something went wrong.
Thanks.
As for versions, it seems transactions in MySQL came with InnoDB, with an acquisition made in 2005 only: In October 2005, Oracle Corporation acquired Innobase OY, the Finnish company that developed the third-party InnoDB storage engine that allows MySQL to provide such functionality as transactions and foreign keys..MySQL 5.0 seems to be stable since 2009, so we can assume everyone has that, I think.
In postgres, I see transaction support back in 8.3 which is also old, from 2008.
Btw, both documentations seem to prefer capital letters. Do both work? Anyway, I'll use capital letters.
5a2ca6e
No branches or pull requests
If one INSERT statement fails for some reason, the previously imported ones should be rolled back. Very useful.
I'm not sure if Postgres and MySQL use the same syntax and since which versions they support it. Expert advice appreciated.
The text was updated successfully, but these errors were encountered: