forums › forums › SQLyog › Using SQLyog › Disable Update When Change Rows
- This topic is empty.
-
AuthorPosts
-
-
December 8, 2011 at 10:45 pm #12533Jason427Member
Currently YOG will update the table if you move off the row that was changed. I see this as a potential problem and would like to disable that. I would like to only have it save when I click the save button. Is there a way to do that?
-
December 8, 2011 at 10:49 pm #32918peterlaursenParticipant
No.
-
December 9, 2011 at 8:22 am #32919peterlaursenParticipant
Let me add that what you should conisder to do here, is to use transactions. You may from the editor execute
START TRANSACTION;
.. next do any number of operation from the Data Grid. It will not be saved to the table. Once you are sure that you want to update the table execute
COMMIT;
SQLyog will still send statements to the server for every row. But the server will not write them to the table – only to a log. On COMMIT the table gets updated. So only after COMMIT other clients will see what you have been doing.
Note that transactions require InnoDB tables and do not work with MyISAM. About transactions in MySQL read: http://dev.mysql.com/doc/refman/5.5/en/sql-syntax-transactions.html
-
December 9, 2011 at 1:48 pm #32920Jason427Member'peterlaursen' wrote:
Let me add that what you should conisder to do here, is to use transactions. You may from the editor execute
START TRANSACTION;
.. next do any number of operation from the Data Grid. It will not be saved to the table. Once you are sure that you want to update the table execute
COMMIT;
SQLyog will still send statements to the server for every row. But the server will not write them to the table – only to a log. On COMMIT the table gets updated. So only after COMMIT other clients will see what you have been doing.
Note that transactions require InnoDB tables and do not work with MyISAM. About transactions in MySQL read: http://dev.mysql.com/doc/refman/5.5/en/sql-syntax-transactions.html
Thank you that will be a big help
-
-
AuthorPosts
- You must be logged in to reply to this topic.