Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Sqlyog Default Changing Parameters

forums forums SQLyog Using SQLyog Sqlyog Default Changing Parameters

Tagged: 

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • #12904
      nicopapa
      Member

      Hello,

      i installed sqlyog on linux mint with wine, the problem i have using it is the following.

      When i make a change in some table and the mouse cursor exits the table cases by default the changes are saved.

      I would like to change this behavior and have to push the save button each time i want to really change something.

      Thanks

    • #34108
      peterlaursen
      Participant

      Currently SQLyog sends an UPDATE or INSERT statement when

      1) user presses save button

      2) when cursor in GRID moves to the row above or below current row.

      And actually I think all GRID based database management tools do like we do in 2). At least I don not know any that don't It is also what users familiar with spreadsheets would expect.

      But I will understand this as a request to queue the UPDATE (and possible INSERT) statements and only fire the statements on save button press. There could also be a preview and edit option (for instance we could open an Editor tab with the statements). Do I understand correctly?

    • #34109
      nicopapa
      Member

      Hi,

      Yes you understood correctly, i hoped there was a way to change this default behaviour of the cursor.

      Sometimes i have to make changes on very sensitive data and this cursor behaviour is one i hope there could be

      options to change it.

      I use also mysql workbench with linux and although i dont like it as much as slqyog, you are forced to click the save button it's time you make a change.

      Hope in the future releases this can be changed.

      Thanks for your reply

    • #34110
      peterlaursen
      Participant

      have you considred using transactions?

      1) Type in the editor “START TRANSACTION;” and execute.

      2) Now manipulate what you want to manipulate

      3) Next either “COMMIT;” or “ROLLBACK;”

      You will then need to use InnoDB tables. What is saved to the server is actually not saved to tables but to a log and only when you COMMIT changes will be written to tables. And only from then on other clients will see the changes you did.

Viewing 3 reply threads
  • You must be logged in to reply to this topic.