Transactions in MySQL allow us to execute any number of queries that will automatically undo themselves if one of the queries fails. This is great because our data is kept in tact if something were to go wrong after the third of five queries.

does this mean (pseudo code):

query(“BEGIN”) query(“UPDATE table SET col=’something’”) //success query(“DELETE FROM table1 WHERE col2 IN (1,2,3)”) //sucess query(“DELETE FROM table WHERE col2=’2 something’”) //fail, ROLLSBACK query(“COMMIT”) // if query #3 didnt fail, it will commit? or will it commit even after rollback?

I was thinking that I should check the result of each statement and executing a COMMIT or ROLLBACK appropriately? but the quote you said on this page seems to make me think I do not need to check the result and that it will ROLLBACK for me? and if it doesn’t roll back, that when it finishes the set of statements, it will COMMIT when I run that statement?

The only reason we are forced to use MySQL is because those guys released it under W$, so all nOObs who cannot tell diff between up and down started using it, and now all serious developers are often forced to use it too. Now Postgresql is released under W$, I was hoping for better times, but it seems too late. MySQL took over big time. :-/

IMHO Postgresql beats mySQL any day.

Sorry for the rant, but this is the zillionth time I hit a wall with MySQL.