[mick]

Yes, it is object browser. Thank you for adding it to issue tracker.

[mick]

'peterlaursen' wrote:

Please try to use the option added in 9.63 for this connection. Please see image for details.

The problem with SET AUTOCOMMIT = 1; is, if I write an update query (which happned to be incorrect because I forgot to add some important where caluse andit modified 1000 rows as opposed to modifying only 10 rows), it saves directly to database. (Oh god that was wrong query) I don't want to do that.

I want to write and run a query and see if it modifies/deletes *expected* number of columns and then execute commit command. so there is no need of rollback.

I am sure this is common expcted feature , people want to commit after making sure the query is correct.

I hope I have explained my situation clearly.English is my second language.

[mick]

'peterlaursen' wrote:

Please execute “SHOW VARIABLES LIKE 'autocommit';”. Does it return ON of OFF?

It is OFF. I have set it OFF under SQLyog connection manager > Advanced > Init commands as SET AUTOCOMMIT = 0; to avoid commit when query is incorrect.

Also, SHOW VARIABLES LIKE 'tx_isolation'; returns 'REPEATABLE-READ'.

I did not follow your post completely, above settings are my current settings. I will explain it again, we have couple developers using SQLyog.

If my collegue modifes something in his sqlyog and I am also connected to database, and I run the query I won't see that change unless I create a new connection and run the query again. And yes, I do execute COMMIT command whenever I really need to save data.

Surprisingly, our web app always fetches fresh data. Our db server and app server are in local network.

Thank you

[Author]

Posts