How to disable automatic update/insert in HeidiSQL when row loses focus - mysql

I am using HeidiSQL 9.3.0.5104. If I insert a new row or change a value when using the table GUI (by clicking in a field and typing in it) and then I click outside of that row, HeidiSQl automatically runs an INSERT or UPDATE for that row without any confirmation. This is especially terrible if you are trying to edit multiple fields in a row and you want to copy and paste each of those values in.
I have looked through all the tabs in the Preferences menu but haven't found anything relating to this "feature". Is there a way to disable this behavior? Maybe there's some sort of safe mode you can run that verifies a query before it executes? When I used MySQL Workbench I had to click an "Apply" button before it ran my queries that were generated from using the GUI. I'd love for there to be a similar feature in HeidiSQL.

Edited - or better said: changed values are displayed with a red triangle in the upper left corner.
To revert your changes, you can either press the "Revert changes" button with the red "X", or press Esc.
To apply changes, press the "Post changes" button on the main toolbar or just click outside the edited row.
There is no way of disabling this "Click outside to apply" behaviour.

Related

How do I prevent a Slate query from running automatically when the Slate document loads?

I have a query and I only want it to run when I click on a button, but not before.
How do I control this?
You can set queries to run manually from the query editor.
Press the button next to Run with the down arrow to get the query options, and check the box next to "Run Manually".
Note: If you set a query to run manually, it will not run on document load or when its dependencies change. It will only run when you tell it to (triggered by event, another query, custom javascript, etc..).

Completely locked up my Access database?

I think I may have completely messed up my application here! I was foolishly playing around with some settings in the File > Options menu for Access and turned a couple of things off. It said I needed to close and re-open, so I did, and now I can't do or edit anything. How do I revert back?
Right clicking the window doesn't help, I tried using Alt+F11 to switch to VBA but that doesn't help. I disabled the close button on the form already, so can't click the X.
I have spent hours working on this, and feel like I may have to start again.
Any ideas how I can get back into my file?
When you double click on the file; hold down SHIFT key.
When you open a database while holding down the SHIFT key, many of the options that you set on the Current Database page of the Access Options dialog box are bypassed.
Once you have bypassed these settings you can access your ribbons and options to reset your settings.

Retrieve Schema for MySQL DB-Connection does not work in Talend

I've created a new MySQL DB Connection, and verified it's OK by pressing the Check button in DataBase Connection - Step 2/2 form.
Then I right-click on the DataBase Connection I created and select Retrieve Schemas.
On the first screen of the Schema form that is opened I leave all default values and press Next.
On the second page the Next button is greyed-out, and no matter what I select/fill on the form it remains being greyed out.
Anybody knows why it may be so?
Thanks!!!
I had the same problem, but you can avoid it.
If you select the CATALOG, the Next button will still be greyed as on attached screenshot. But if yo will expand the CATALOG and Sellect All, the Next button will be active.
I had this same issue, in order to resolve it I needed to generate database diagrams and then verify that talend could see all the tables I was looking to retrieve. Basically if you cannot expand any schemas it means there is nothing to import.

Is it possible to open more than one query tab without opening another connection via Alias in Squirrel SQL?

I keep commenting out my queries in the SquirreL SQL client, but I also have been opening new connections using other Aliases, however it all gets a bit crowded in the tab area.
I've also been able to save my queries in files, which works great except for the fact that the entire path to the file (often very long) appears in the tab.
Is it possible to just have another SQL tab opened, or might there be a way to simplify how many SQL query tabs I open?
I hope, the answer will be still useful, although the question is asked some times ago :-)
Is it possible to just have another SQL tab opened, or might there be a way to simplify how many SQL query tabs I open?
You can open a new SQL-Worksheet for the current session.
Try one of the following:
Shortcut CTRL+N
Menu Session >> New SQL-Worksheet
In the toolbar, the icon right of the rollback button.
I've also been able to save my queries in files, which works great except for the fact that the entire path to the file (often very long) appears in the tab.
This changed in 3.4.0. Please see the changes
Instead of displaying the file paths in Session tabs a small button is displayed when an open file exists.
Clicking the button will open a popup menu that gives access to several information and functions concerning the file.

Is there a design pattern for this...?

When a user selects a record in a datagrid I launch a pop-up window with more detailed info. The user can make changes to the record in this window but they don't have to save them. For example, they can click the X to close the window.
Unfortunately, I am stupid and whenever a user makes changes I update the object directly.
Is there a pattern for copying the object and then mapping the changes to it when a user confirms they want to save?
Thanks!
I wouldn't go with copy and merge. Why don't you just update the object only if the user explicitly wants to update/save? Let the UI be UI and condense the relevant information from it as soon as you need it.
Another way that may be appliable, if you want something like temporary edits, would be using commands for every atomic update, where every command has an inverse - undo - command. If you keep these in a history, you could just go back to the initial state.