Skip to main content

Archlinux MySQL Workbench result grid

Introduction

I run ArchLinux for a while and one of my key software is MySQL Workbench.
Unfortunately, I did not get it working for a while.
Dont worry, it's working now, and this is my attempt to collect the informations in order to try to know what happenned.

What did not work

Several week after having a base Archlinux installation working, I managed to install MySQL Workbench from AUR.

The software behaved correctly except the result grid never displayed: I just got a blank grid, but when switching to the edit form the data were there. Data have been correctly retrieved and can be edited, but the problem was on the result grid display.

It was version 6.1.6 at that time, arround the end of June 2014.
I recompiled "mysql-connector-c++", "ctemplates" before building mysql-workbench: no way, no result grid.

I even tried to compile Mysql Workbench development version (6.2 at that time) against AUR  "mysql-connector-c++", "ctemplates" but no way: no result grid.

As far as I really needed some GUI to manipulate MySQL, I used Squirrel.SQL.

What made it works

Some time later, on the Mysql Workbench AUR package comments, I noticed there was a bunch of upgrades: Mysql Workbench was 6.2.3, and there was a glib2 patch!
Wait.. glib2? This Glib2? Great, let's try it now!

I upgraded "glib2" via "pacman" (as I keep my system up to date, it was already the latest available), then rebuilt "mysql-connector-c++" and "ctemplates" (just to be safe), then rebuit "mysql-workbench".

Guess what? I finally got the result grid!

What was wrong?

To be honest, I did not find any related information either in the mysql-workbench nor the Glib2 release notes. I don't understand what was not compatible, what did not work together, what was conflicting?

I'm writing this blog post in order to try to collect information about what happened. SO, folks, if you ever know: please tell me!

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo...
Read more

wget maven ntlm proxy

How to make wget, curl and Maven download behind an NTLM Proxy Working on CentOS, behind an NTLM proxy: yum can deal without problem with a NTLM Proxy wget, curl and Maven cannot The solution is to use " cntlm ". " cntlm " is a NTLM client for proxies requiring NTLM authentication. How it works Install "cntlm" Configure "cntlm"  by giving it your credentials by giving it the NTLM Proxy Start "cntlm" deamon (it listens to "127.0.0.1:3128") Configure wget, curl and Maven to use "cntlm" instead of using directly the NTLM Proxy Note: You will have then a kind of 2 stages Proxy : cntlm + the NTLM proxy Configure CNTLM After installing cntlm, the configuration file is in "cntlm.conf". You must have your domain (in the Windows meaning), proxy login and  proxy password. Mine are respectively: rktmb.org, mihamina, 1234abcd (yes, just for the example) You must have you NTLM Proxy Hostnama or IP ...
Read more

VMWare Keyboard Latency

Workstation VM UI lag when typing When using a VMWare Workstation VM, I noticed there is a latency when typing in the keyboard and the real appearance of the typed character. I searched and found: Noticeable typing lag in Linux VM terminals since v16.2 upgrade on Linux host To make it short, what solved it for me: Disable 3D acceleration in the VM setting .
Read more