When I kill a query or connection, whoever is running it gets a boring message about what happens. Wouldn’t it be fun and useful to be able to specify the error message the user should see? Imagine the possibilities:
mysql> KILL 10282, "Sorry, no cigar today. Try again tomorrow."
Joking aside, relevant error messages would be great for all involved.
Further Reading:
I’ve used this on the :inux command line a few times (Provided the database isnt too big ;p )
$ mysqldump salika –extended=FALSE | grep jack | less -S
SkySQL is Looking for a Senior Marketing Manager for North America!
If you or someone you know is looking for this kind of position, then this is a great opportunity.
I’ll spare all of the details, but if you’re interested, you can read more about the position here:
http://www.skysql.com/content/senior-marketing-manager-north-america
And as always, you can view all of SkySQL’s open positions here (as we’re also looking for Engineers and Consultants):
http://www.skysql.com/company/careers
“What will you do if one day some one ask you to find single string in all databases, all tables and in all columns?”
— This was asked to me once. There is some string in the database but I do not know where. There was a task to find an user’s details which is in the database which consists of many tables. And all I know is only the user name and do not know any other details. How am I supposed to find that string? I do not want to write some complex SQL for this. Digging more into this, I came across few GUI tools for MySQL which have good search feature.
So I am writing this blog about search feature in those tools. I shortlisted three client application for MySQL:
1) SQLyog
2) phpMyAdmin
3) HeidiSQL
…
[Read more]As Patrik noted last week, MariaDB is taking a leading role in the trend of keeping the MySQL ecosystem an open one. The SkySQL and MariaDB teams work together closely on this, and we even travel together!
Join both SkySQL and MariaDB at this week’s LinuxCon North America conference in sunny San Diego to learn more about how MariaDB is directly communicating with users (including SkySQL enterprise customers) to not only identify and help fix issues with current releases of the MySQL database, but to also further enhance MariaDB to become even more technologically advanced.
On the 8/16 I conducted a webinar titled: "Scale Up vs. Scale
Out" (http://www.slideshare.net/ScaleBase/scalebase-webinar-816-scaleup-vs-scaleout):
ScaleBase Webinar 8.16: ScaleUp vs.
ScaleOut from ScaleBase
The webinar was successful, we had many attendees and
great participation in questions and
answers throughout the session and in the
end. Only after the webinar it only occurred to me
that one specific graphic was missing from the webinar deck. It
was occurred to me after answering
several audience questions about "the difference
between …
MySQL 5.1 added a long-needed feature: INFORMATION_SCHEMA tables for inspecting locks held and waited-for inside of InnoDB. With this addition, it became possible to figure out who is blocking whom.
MySQL 5.5 changed a lot more things inside the server. One of the
new features is improved metadata locking. This solves a lot of
inconsistencies and bugs that were previously possible. The
output of SHOW PROCESSLIST is also changed; instead
of the venerable Locked status, there are more
fine-grained status indicators such as Waiting for table
metadata lock.
Unfortunately, the additional locking is not possible for the DBA to inspect. Where InnoDB’s storage-engine-level locking used to be …
[Read more]People often assume the reason I talk at conferences is because I like to teach them about Galera, MySQL and other cool, open source things. That's of course true to some extent. But for me personally, another reason is even more important: It happens almost always that the audience teaches me something. Thus the process of public speaking has increasingly become my way to learn new insights. Low level details that aren't easy to learn by just RTFM.
We finally got the MySQL Connector/Python repositories reorganised on Launchpad. The following changes have been made: