the "f" parameter in the UNIX tail command stands for "follow". Probably you have used it for logfile monitoring, a fantastic feature!

Now you can do the same in a MySQL table, using HeidiSQL: Just click Tools > Auto-refresh > Active (or press Ctrl+F5) to start monitoring a table's data:



This feature has been implemented moments ago. Select Help > Check for updates in HeidiSQL or go here to get the latest build.

I had to disable write access for anonymous mantis account because of the spam in comments. Will enable it one I add some kind of protection. For now - please register to report a bug. Thanks.

FYI, we've now added an Italian section on Planet MySQL: http://it.planetmysql.org

If you are a MySQL enthusiast from Italy and would like to start blogging about it in your native language, please consider submitting your feed for inclusion!

Giuseppe just recently started blogging in Italian as well and has already added his feed there.

FYI, we've now added an Italian section on Planet MySQL: http://it.planetmysql.org

If you are a MySQL enthusiast from Italy and would like to start blogging about it in your native language, please consider submitting your feed for inclusion!

Giuseppe just recently started blogging in Italian as well and has already added his feed there.

“Leap seconds” are starting to cause questions on our forums and in some bug reports because ‘2008-12-31 23:59:60′ will be the first leap second in the last 3 years. We have a short answer and a long answer.

The short answer is: it will only cause a problem if you
(
(
(a) arrange so your operating system returns the leap-second value for MySQL to see,
or
(b) load the appropriate ‘leap second’ tables as described in our manual,
)
and
(c) do something which uses the NOW() or CURRENT_TIMESTAMP at precisely midnight UTC on December 31 (remember your local time is not UTC time!).
)
or
use CONVERT_TZ() or FROM_UNIXTIME().

Even if those unlikely things occur, you can kludge the results next day. So don’t worry. My colleague Dmitri Lenev points out: there are leap -second geeks who are configuring their systems to have non-posix unix …

I moved all the QOT code to Launchpad. This includes code for the tool, tests and a small experimental utility qot-predictor, which based on query analysis tries to predict which queries are likely to be executed next. Project URL for branching is lp:qot. If you want to push your own changes just create a new project branch.

The MySQL database server can display a lot of performance statistics. However, most of them relate to general server parameters, such as buffer sizes and query cache settings. Of course, such settings are important to get right, and can make a huge difference in performance. Once you've tuned them however, you need to start looking at the tables and queries. When a single bad query can cost 90 - 99% of the total performance, server tuning doesn't fix the problem. But obtaining query profiling information from MySQL can be tricky. Here are some of the options:Slow query logYou can use the built-in slow_query_log from within the server. It will show you queries that take more than a second. Such queries typically don't use indices properly and are important to address. But only slow queries end up there, and many performance problems aren't caused by slow queries, but by queries that are run very often (for example, for-loops in the code …

Today we released Jet Profiler for MySQL for beta testing!

Jet Profiler for MySQL is a query profiling tool, focusing on running queries and processes. It can provide top lists of the most frequent queries, tables, schemas, users and more. Such top lists help you identify bottlenecks and fix the worst performing parts of your application.

We are looking for 20 people who would like to beta test it and give us feedback. If you like profiling MySQL databases, or are curious to know what bottlenecks your site might have, please go to our beta page to receive download links and key. Use the following promotion code:

I LIKE MYSQL


2 Comments

Last week I attended the International PHP Conference 2008 in Mainz in Germany. The conference was well prepared and I would like to say thanks to organizers. There was just one thing, which could be better. It was raining for all my stay, but this nobody can influence:).

As I expected, almost nobody from the attendees knew the PHP support in NetBeans or NetBeans itself. PHP support in NetBeans is still new and the first version of the PHP support will be released with NetBeans 6.5, probably next week. Because our tool is still new for PHP developer, no surprise for me. I met probably less people than I have fingers, who knew NetBeans. Sun was one of the Gold sponsors and during opening ceremony the audience was asked whether there is someone who knows the PHP support in NetBeans. I think that there was  6 people who put up hand.

On Wednesday I had one session, where I did demonstration of features that are available in …

Today, the site was officially launched!

Soon, we will make the beta version of Jet Profiler for MySQL available to selected users! Contact us if you are interested.


Comments