Hi I have the following bug on pgAdminIII:
If I open the SQL Query tool page none of the buttons are visible and only if I go over the upper line some of them become visible. But I can't write or execute any query.
I tried to uninstall it and reinstall it many times also with other version but the same thing happens all the time.
Did anyone experience the same problem?
Yes it is a bug. Try the View -> 'Default View' in the Query window as an alternative way. Also update pgadmin and check.
Related
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 new to MongoDB Compass tool and am trying to update a field in my collection. Please can someone suggest where the update query must be written. Could find no options or panes in the tool to write custom queries be it selection / updation for that matter.
In the Default Window only the selection/projection/restriction options are found.
Any help is much appreciated.
In the latest version, there is a "_MongoSH" in the bottom left corner of the window.
Thx to #Boštjan Pišler for the hint about a new feature.
Old answer:
I had the same issue, it looks like a simple feature to implement (since document updates are possible) but... AFAIK there is no such option in compass, you can do it through mongodb shell (CLI client).
The tool was recently updated with a shell (currently in beta) which is accessible by clicking the dark bar on the bottom of the window "_MongoSH"
At the bottom left, _MONGOSH:
There you can call updateMany and any other methods available in the MongoSH syntax
You can use mongo MongoSH. Currently its in Beta.
Just move your mouse over a document and find a little pencil. You will enter in update mode. You can change fields, values, arrays, etc.
I have installed MySQL Workbench (v 6.3.9) on my mac macOS Sierra 10.12.4.
There are several problems with displays.
I do not have access to export options in "Forward Engineer SQL Script", there is no text in the catalog in the left panel (and more...).
What can I do to workaround these problems?
You're correct, MYSQL Workbench (v 6.3.9) is buggy, though it is still possible to do Forward Engineer through Database->Synchronize Model. An alternative to viewing the text in the catalog is clicking the layers option on the right to display your tables.
Cheers!
Every software has bugs, it's just sometimes less obvious (here however very). No doubt, both are serious problems. The first one is already known and we will fix it for the next release. The second problem however is surprising. I just tried the version available from the MySQL website and the catalog tree shows fine for me. Would be good if you could create a bug report for that, so we can fix that too.
Ok, so this may seem like a stupid question but I'm fighting DBeaver and so far it's winning and Google is refusing to pick a side.
I've worked out how to explore the database, view the structure of tables, I can even view the data of a table and filter it.
But if I just want to run an arbitrary SQL statement how do I do that?
And 30 seconds after posting I found the answer. There is an SQL Editor menu appeared at the top of the screen (not in the Database Navigator). Selecting SQL Editor from that brings up a query window I can type SQL into.
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.