When I query a table in MySQL Workbench, no results are shown, the result section is just blank, no grid or anything. However if I export the data, it is all there. Everything worked fine until a couple days ago.
Query settings:
Max Length = 65536
Continue on SQL Script Error = true
"Safe Updates = true
Leave autocommit mode enabled = true
Progress status update interval = 500
Default algorithm for ALTER table = Default
Default lock for ALTER table = Default
Limit Rows = true
Limit Rows Count = 1000
Max Field Value Length to Display = 256
Treat BINARY/VARBINARY as nonbinary character string = false
Confirm Data Changes = True
No queries work, an example would be SELECT * FROM database.address
This is a known bug: link.
Upcoming release 6.2.2 fixes this for OS X (Unfortunately, Linux version is still broken).
At least on my computer it's not dissapeared, just folded, and it's edge is almost merged with the edge of 'Action Output' block. When you move your mouse to that edge, the cursor starts looking like a dash with two arrows. Slowly move it couple of pixels higher until you catch the small 1px area where the cursor changes to a dash with a single arrow. Then catch it and pull : )
I've made a couple of photos to illustrate this.
New to MySql myself and found this is happening on Windows as well. Goto Query > Explain Current Statement > click on the Results Grid icon on the far right of the Visual Explain window that shows by default. You may have to toggle through the up down arrow icons to see it.
I had the same problem after upgrading to Ubuntu 14.10. I found this link which describes the steps to be followed in order to apply the patch. It takes a while since you have to start all over again: downloading, building, installing... but it worked for me! Sorry I'm not an expert and I can't provide further details.
Here are the steps described in the link above:
If you want to patch and build mysql-workbench yourself, get the source from for 6.2.3. From the directory you downloaded it to, do:
wget 'http://dev.mysql.com/get/Downloads/MySQLGUITools/mysql-workbench-community-6.2.3-src.tar.gz'
tar xvf mysql-workbench-community-6.2.3-src.tar.gz && cd mysql-workbench-community-6.2.3-src
wget -O patch-glib.diff 'http://bugs.mysql.com/file.php?id=21874&bug_id=74147'
patch -p0 < patch-glib.diff
sudo apt-get build-dep mysql-workbench
sudo apt-get install libgdal-dev
cd build
cmake .. -DBUILD_CONFIG=mysql_release
make
sudo make install
Hope this can be helpful.
It was really frustrating as it was still happening in the workbench version 6.3.10 (for mac) available in the mysql official site (here).
I got it resolved by first collapsing the bottom panel (check the top right in the attached image (termed as collapse button)) and then pulling up the empty region from the bottom.
Now if I again click on collapse button this time result grid is visible along with the action grid.
The problem, as it is described, corresponds exactly to the bug MySQL Bugs: #74147: empty grid result, incompatibiliity with libglib_2.42
The good news is it's almost closed.
A patch is available since today.
EDIT :
In Debian Jessie (testing), the problem is solved with the package mysql-workbench 6.2.3+dfsg-6 available since today.
Update manually from mysql website
Here's a solution for Ubuntu 15.04 users running Mysql Workbench 6.2.3.
I was able to resolve the issue of missing results in the Mysql workbench by just upgrading mysql-workbench to version 6.3.3 from http://dev.mysql.com/downloads/workbench/. You will need to download the one marked for Ubuntu 14.10. An install via Ubuntu software center resolved the issue. Hope this helps.
This was still happening to me on version 6.3.9 on OSX. I downloaded 6.1.7 again to actually see the result grid again.
What a pain in the butt!
The easiest fix for me to see the Result Grid again was to click on Explain Command
[
After that Execution Plan is going to be shown and on the right side you can click on Result Grid
I'm using MySqlWorkbench 6.3.9 on macOS and has this problem. I removed the app and installed 6.3.10 which solves the problem.
If you do not want to compile it yourself you can go to:
Applications→Ubuntu Software Center→Edit→Software Sources→Updates
there you can check hardy-proposed is ticked(for 14.10 will be utopic-proposed)
Source
then simply go to terminal and type:
sudo apt-get install mysql-workbench
As a note, you will get other updates to, witch may not be stable!!!
MySQL Workbench 6.3.4 fixes this issue. Custom builds are not needed anymore.
http://dev.mysql.com/downloads/workbench/
The result set wasn't showing for me either. I was able to make it appear by hiding the output area and running a simple select statement. Then I "show"ed the output area again and had what I was looking for -- both the result set and the output area
I was able to solve this issue by doing the following...
Go to the MySQL website for Workbench: https://dev.mysql.com/downloads/workbench/
Once there scroll to the bottom of the page and click on the tab that says "Development Releases"
Select your platform, download & install
You will likely want to uninstall any workbench packages already installed. GL!
I had the same issue. Using MySQL 6.1 Workbench.
After a while (2 mins), it just crashed. Reported bug, saved files and reopened. It works now.
I guess I would suggest if that happens again, to immediately save the open scripts, close MySQL and restart it.
The problem is with the TAB. From the tab's title I assume you first made a right click > "Select Rows - Limit 1000". But when you enter a different query in the opening tab, it won't show anything any more... Don't know why. Open a new tab for manual queries, then it will work.
I have updated macOS to 10.13.4 and it works.
I searched for almost an hour, tried everything, restarted Workbench, upgraded Workbench, used the "explain query" trick, but nothing worked.
The explanation for the result grid not showing anymore was actually very stupid: there was a INSERT INTO mytable few lines above the SELECT query. I share it anyway because it might help some other people.
I had this problem too. I think it is a problem "screen size" related. Some Workbench versions present this problem, accordingly the numerous other answers.
However, I'd solved this by simply lowering the monitor resolution and the Result Grid has back to be draggable with the mouse pointer (very like the Thaumant answer already indicated).
I've taken these photos to illustrate what I'm saying.
At 1440x900 the Result Grid draggable selector are not being showed...
Now, in 800x600 resolution (with 125% of scale) the Result Grid has back to be draggable !
Works too with greater resolutions along with bit of scaling*
Related
I'm new to octave (and any kind of programing in general). It doesn't matter the code that I run, every time i do it the command window displays every line of it and every step, which can get overwhelming when doing cyclical algorithms. And this doesn't seem to happened to every other user I personally know. Even using exactly the same .m file, i get all the lines displayed and some other person doesn't.
I've searched in every configuration window possible, I tried reinstalling but nothing helped. And I've seen nobody else having this problem, is it just a configuration that I'm not aware of?
I'm running Octave 5.2.0 in Linux Mint 19.3
have you tried adding ";" at the end of your command lines ?
Basically if your code is something like:
x=5
y=4
Then your command window will display:
x=5
y=4
Whereas if you add the semicolons at the end of your code like so:
x=5;
y=4;
Then your values will be store and registered but nothing will be displayed in the command window.
I attempting to edit Windows Terminal's JSON config file:
When I save, the document is minified:
I only have two extensions (I have removed others and restarted vscode). How do I find out where the minification is occuring? How do I stop it?
This is a bug in Windows Terminal. It's now fixed in the current Preview release. Mike Griese from Microsoft answered this via GitHub:
The profiles.json thing is a temporary thing. Unfortunately, Windows.Data.Json always writes out json as a single line, without the ability to pretty-print it, and we re-write the profiles.json to make sure that it stays up to date with the schema of the app. So currently, it'll keep re-writing it. But that's a huge pain point that we want to fix ASAP.
I currently have 1.23.1 installed and would like to update to ´1.30´ and got bunch of extensions installed. What would be the best way to update the wiki? Should I update version by version or jump straight the the final version that I want?
There is no real benefit in updating version by version; the upgrade script just applies DB schema changes from each version successively, so mostly the result will be the same both ways. If something breaks, going step by step and testing after each step will tell you which version broke it, and thus you are in a better position fixing/reporting it, but it's usually not too hard to figure that out anyway and it would be a vast time sink.
So after switching over to Sublime Text last year, it has become my editor of choice, and I have installed several different packages via the excellent Package Control and basically customized it all to my liking. After a couple months of infrequent use, I jumped back into a code-intensive project and fired up ST2 only to find that none of my packages are working.
After some digging, it finally occurred to me to open my preferences file, only to find all of my installed packages in the "ignored_packages" list. WTF?
Has anyone else experienced this or know what would have caused this? I do some funny things in my sleep sometimes, but not this!
My earlier comment notwithstanding, I think I've figured out what's going on. The issue seems to be Package Control, most likely the new version update to 2.0. I just restarted ST2 after having it open for the past few days, and happened to have the console (Ctrl`) open, and saw that several of my packages, including Tag, Terminal, and SublimeREPL, were added to the ignored packages list. This typically happens when a package is being updated or removed, and is done so it can't be used halfway through the operation before everything is synced. At any rate, for me there was some sort of error, and I had to force quit Sublime and restart it. I immediately checked my preferences, and sure enough several packages were in the "ignored_packages" array.
So, I'm guessing something like this happened to you, and for whatever reason the packages weren't removed from the ignored list, possibly because the system update didn't complete normally. Hopefully this won't happen again, but if it does you'll know where to look. Additionally, if it does happen again, I'd submit an issue on Github, as this may be a bug.
Update
My issue on Github has been merged into this one, and if you scroll all the way down to the bottom wbond has a fix for now: Download Package Control 2.0.1-beta, put it in your Installed Packages folder (removing the one that's already there), and adding the repository https://sublime.wbond.net/prerelease/packages.json by selecting Preferences -> Package Control -> Add Repository. Restart ST2, and see what happens, especially after restarting multiple times. If you still have bugs or odd behavior, please add to the issue.
I am adding this even if it's an old thread because the answer did not solved my problem, but it pointed me in the right direction.
Since it was a problem due to Package Control trying to update packages and I didn't want to mess with repos and stuff, first I tried to upgrade the packages "manually" using Package Control and I noticed that there was a 1-to-1 match between the items in the ignored_packages array and the packages that needed to be upgraded.
After updating, just remove the packages from the array and restart ST2: no more weird ignored packages in the array.
Does anyone know how to get MySQL transactions working under Mono?
I'm using MySQL Connector/NET (via Subsonic 3) and it works perfectly under Microsoft .NET. Recently however I tried running the same site under Mono on Ubuntu and it almost works - except I can't seem to get transactions working.
Reading around the Mono/MySQL sites it's not exactly clear what is and isn't supported.
The original problem is a NotImplementedExcetion with call stack like this:
[System.NotImplementedException]: The requested feature is not implemented.
at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction (System.Transactions.Transaction) <0x00181>
at MySql.Data.MySqlClient.MySqlConnection.Open () <0x00381>
at SubSonic.DataProviders.DbDataProvider.CreateConnection (string) <0x00059>
at SubSonic.DataProviders.DbDataProvider.CreateConnection () <0x00015>
There's a few mentions of this on the MySQL site which seem to point to Mono not supporting the required infrastructure to make transactions work. There's also a comment that transactions work fine when using CommittableTransaction rather than TransactionScope. So I tried that, but got the same exception.
Another comment on the MySQL site suggested rebuilding the MySQL data provider with the MONO build option. Which I tried and the site now works, but transactions aren't being used - they've been simply disabled. Really?
I find it hard to believe that transactions can't be made to work in this environment, but can't find a working example.
Mono 2.6.7, MySQL Connection/NET 6.3.4, Subsonic 3, Ubuntu 10.10
Figured it out. It's TransactionScope that doesn't seem to work. Reverting back to DbConnection.BeginTransaction works fine. I've written up how to do it under Subsonic here: http://www.toptensoftware.com/blog/posts/18/using-transactions-with-mono-mysql-and-subsonic
I also had this problem with mono v.2.10.9 and mysqlconnector v. 6.6.5 and 6.7.2-Beta and I was unable to find a solution for this problem but now I figured it out.
First I took the sources of mysqlconnector and added them into my project folder. Thought it would work if I compile the connector directly with mono but it doesn't.
Then I stepped trough the code and I found that there are the following lines of code at line 530 in the file Connection.cs of the MySql.Data project:
#if !MONO && !CF && !RT
Console.WriteLine("### Should not be here... ###");
if (Transaction.Current != null && Settings.AutoEnlist)
EnlistTransaction(Transaction.Current);
#endif
The Console.WriteLine was added by me to try if it will also appear if I run my Application with mono and it appeared. So I commented this lines out and after that everything was working at this moment.
The real solution however should not be to comment out some lines of code.
For solving this you have to define the 'MONO' symbol.
If you are using MonoDevelop just right click on the project MySql.Data and select the compiler section. There you will find a textbox with the label 'define symbols' or something similar. Simply add the new symbol 'MONO' into this textbox.