The story of Steven Mapes, an experienced software developer who
has been using SQLyog MySQL GUI since 2002.

We were so thrilled to speak with Steven Mapes for two simple
reasons. One, he is an ardent user of SQLyog. Two, he has been
using the tool since 2002 (we had released the GA version of
SQLyog in 2002). And, it is users like Steven who make the
product successful with their constant support and feedback that
keeps us going.

We go down memory lane and learn some interesting facts about
SQLyog that made Steven stick with the tool for more than a
decade.

Steven Mapes is a self-employed software solutions provider who
develops web-based polyglot solutions for clients often hosted
within the cloud since 2012. Before it, he was the Head of IT for
Moko Social Media in the UK. When asked about how he came across
SQLyog and the need to use the tool, Steven says,”My first
exposure to SQLyog was back in 2002 when the …

In the quest to secure MySQL as well as ease the number of
complicated passwords to remember, many organizations are looking
into external authentication, especially using LDAP. For free and
open source, Percona’s PAM authentication plugin is the
standard option.

The mysql client is a tool which I use every day
as a DBA. I think it's a great tool. When I used a client of
several other SQL and NoSQL databases I was quickly reminded of
all the features of the mysql client. Note that psql (PostgreSQL
client) is also very nice.

Some other interesting things about the mysql client: It is build
from the same mysql-server repository as MySQL Server. The source
is in client/mysql.cc. In addition to the server
version it also reports 14.14 as its version. The previous
version (14.13) was around the time of MySQL 5.1, so this version
is mostly meaningless.
If you start it it identifies itself as "MySQL monitor", not to
be confused with MySQL Enterprise Monitor.
The version of the client is not tightly coupled with the …

As work on WarpSQL (Shard-Query 3) progresses, it has outgrown
MySQL proxy. MySQL proxy is a very useful tool, but it
requires LUA scripting, and it is an external daemon that needs
to be maintained. The MySQL proxy module for Shard-Query
works well, but to make WarpSQL into a real distributed
transaction coordinator, moving the proxy logic inside of the
server makes more sense.

The main benefit of MySQL proxy is that it allows a script to
“inject” queries between the client and server, intercepting the
results and possibly sending back new results to the client.
I would like similar functionality, but inside of
the server.

For example, I would like to implement new SHOW commands, and
these commands do not need to be implemented as actual MySQL SHOW
commands under the covers.

For example, for this blog post I made a new example command
called “SHOW PASSWORD”

New SSL alternatives SSL connections in previous versions of
MariaDB Connector/C based on the OpenSSL library. The OpenSSL
heartbleed bug, licensing problems and the lack of supporting
different transport layers were the main reasons that we decided
to offer SSL alternatives. In addition to OpenSSL the following
SSL libraries are supported in Connector/C 3.0: GnuTLS […]

The CVE-2015-0204 FREAK SSL vulnerability abuses
intentionally weak “EXPORT” ciphers which could be used to
perform a transparent Man In The Middle attack. (We seem to
be continually bombarded with not only SSL vulnerabilities but
the need to name vulnerabilities with increasing odd names.)

If the result is 0; the server is not providing the EXPORT
cipher; and as such is not vulnerable.

Is your client vulnerable?

Point your client to https://oneiroi.co.uk:4443/test if this
returns “Vulnerable” then the client is vulnerable, if you find a
connection error your client should not be vulnerable for
example:
root@host:/tmp$ openssl …

One of the great features of Shard-Query is the ability to use
MySQL proxy to access resultsets transparently. While this is a
great tool, many people have expressed reservations about using
MySQL Proxy, an alpha component in their production environment.

I recognize that this is a valid concern, and have implemented an
alternate method of retrieving resultsets directly in the MySQL
client, without using a proxy. This means that any node can
easily act as the “head” node without any extra daemon, instead
of having to run many proxies.

The sq_helper() routine has been checked into
the git repository and is available now.

Chuck Bell, one of my former colleague from MySQL AB, has created
a connector for Arduino to MySQL. So this allows Arduino code to be a
direct client of a MySQL or MariaDB server, with Ethernet and
WiFi shields supported.

With Arduino boards being used more and more, this can come in
really handy – not only for retrieving (for instance) centralised
configuration data, but also for logging. Useful stuff. Thanks
Chuck!

If you need to link into non-GPL compatible code, there is the
(slightly larger and full featured) libdrizzle library. But if
you want something *tiny* and are okay with GPL, then nanomysql
may be something to look at.

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.