I was working with MySQL Workbench to continue a schema I had started yesterday. After some work, I created a new EER Diagram and put some of the tables in it. Suddenly, I believe after pressing Ctrl+Z, the whole thing rolled back to where I started and every table I had designed was now called "table1" in the schema.
Is there any way to recover the work lost?
Thanks in advance.
In MySQL Workbench you can, like in many applications, undo changes and of course redo them -> see the Edit menu. Shortcut for redo is Shift+Ctrl+Z on Linux + Win, Shift+Command+Z on macOS.
Related
I've just run a couple of queries where I forgot to click on the blue 'refresh' button when I launched Oracle SQL Developer.
But I was wondering whether it actually refreshes anyway, when you actually launch it?
Short answer: 'no.'
But first, let's share with folks with the 'blue refresh button' you mention in your question.
What does this button do?
It re-executes the query that the resultset is tied to, in this case
select * from employees
When you restart/re-open SQL Developer it does not even connect to any databases, much less re-execute any queries automatically.
What you might see is a .SQL file re-opened as you had it open when you closed the application from your last session. But no database work will happen until you hit the 'Connect' button.
Disclaimer: I work for Oracle and am the product manager for SQL Developer.
I am attaching the image of what I see at opening MySQLWorkBench for a particular connection. Previously, on the left pane I saw the expandable list of the tables, now I see the empty pane.
The change was in the username/password for standard TCP/IP over SSH connection method for connection to AWS RDS.
Is it possible to see the list of the tables again? Maybe I changed accidentally some MySQLWorkBench settings?
I have MySQL Workbench 8.0, version 8.0.19 on my MacBook Pro. Try to hover your mouse in this area shown here (with the red arrow):
Then click, hold, & drag down to reveal the tables:
Go to Edit and open Preferences
Select SQL Editor and check both options under sidebar. Click OK.
Hopefully, it will solve your problem. To answer this question, I took help from here
Check out this answer here. Their problem appears to be the same as yours.
I recently installed MySQL Workbench 6.3. When I write queries the Beautify/Reformat option works fine. But that's not the case when I write stored procedures. If I click the corresponding button nothing happens and also the menu in Edit -> Format is inactive. Since it is a useful feature I would be very grateful if someone could give information about this issue. Is it probably related to the specific version of MySQL Workbench or are there any settings that should be altered, etc.?
Thank you in advance.
After filing a bug report at bugs.mysql.com it was confirmed that the problem was associated with the specific build of the MySQL Workbench 6.3 which was not the last one. This problem does not exist in later versions, for example the current newest version which is 8.0.13.
I'm following a tutorial to learn MySQL and I'm supposed to paste a text file into the Editor Window in Workbench to create tables, then populate them with another text file. I'm using MySQL Workbench 6.0.8 and I don't know where the Editor Window is. Haven't found a space that takes the pasted text. Could someone please tell me where the Editor Window is for starters? If you could give me some guidance to set up the tables in Workbench 6.0.8 that would be wonderful too! I've looked around online for a couple of hours to no avail. Thank you.
Not sure which tutorial you are following, but try the one from MySQL which explains all 3 major parts of MySQL Workbench (administration, modelling, SQL work). The administration chapter shows how to create and open a connection while the last one then shows how to query tables, add data etc.
I know this question may be seen as a duplicate with this one. I even have almost the same configuration (PostgreSQL 9.1.3, pgAdmin III 1.14.3, 32 bit Windows). What is the difference and the reason I ask a new question is that my PgAdmin doesn't crash always (just mostly) and that the cause of the problem is different - in linked question the problem was with missing adminpack, but I have adminpack installed and it works well, so the answer for linked question doesn't work for me.
Do you have any ideas where the problem could be?
EDIT: PgAdmin doesn't crash at other occasions (well, unless I do someting that obviously deserves a crash), just while trying to open SQL query window. It's worse and worse as time goes on, now it's almost "always". The problem is not "connection specific" - frequence of crashing is the same for different server connections.
EDIT2: I reinstalled PgAdmin and nothing have changed. I'm starting to suspect PostgreSQL 9.1.3 or even PostGIS 2.0.1 of the problem.
Goto run and type %appdata% and go inside postgresql folder.
rename or delete pgadmin_histoqueries.xml file.
try opening the SQL query editor again.
Good luck!
PgAdmin crashes on me all of the time, but you eventually learn to be gentle with it.
Particularly, if it is waiting for a response from the PostgreSQL server, the window may freeze up until a reply is returned and parsed. When this happens, do not close the window, just wait.
Also, if you attempt to edit two different objects on the same parent, save one and click save on the other, this crashes the program.
My advice would be to only do one thing at a time, be patient, and don't be in a hurry to kill the process when it freezes up.
There can be a great many different possible reasons for crashes. Some of them have been fixed in the latest version 1.16.1, release just last week.
You could try the new version and see if that fixes your problem.
Pgadmin3 was really unstable after installation on my ubuntu 12.04 LTS. It either freezes or crashes even while doing very basic things like looking data in a table or list tables in a schema etc., I almost gave up and started using the command line psql and luckily stumbled on this blog which recommended to remove the pgadmin3 history file to solve the freezes and crashes. It worked for me.