April 16, 2014

MySQL 5.1 Command line client improvements

Just found this little handy feature today:

So now if you press CTRL-C MySQL Command Line Client will not exit but will terminate query being executed. This is great as so many queries assumed CTRL-C would also abort running query in previous MySQL versions and I’ve seen many monstrous queries left running without noticing just because people would think CTRL-C terminated the query. Now it finally really does.

Great Job! I wish I would see more of such relatively simple but very handy improvements :)

About Peter Zaitsev

Peter managed the High Performance Group within MySQL until 2006, when he founded Percona. Peter has a Master's Degree in Computer Science and is an expert in database kernels, computer hardware, and application scaling.

Comments

  1. Paul DuBois says:

    This was introduced in 5.0.25 (and 5.1.10).

    http://dev.mysql.com/doc/refman/5.0/en/news-5-0-25.html

  2. jim says:

    i did that.

  3. Harrison Fisk says:

    I helped with it ;)

  4. jim says:

    that’s right! i forgot that what i did was based on harrison’s initial patch.

  5. peter says:

    Thanks Jim, Harrison, Paul

    It may have been where for a while I just somehow did not notice it before :)

  6. Perrin Harkins says:

    I agree: great feature! Very helpful.

  7. Moazzam says:

    You guys rock! It’s very handy. Using that you can even do a select and an insert in the same query from the same table. It randomly messes up the MYI files, though (which can be repaired by table repair command). It would be great if it didn’t.

    I did something like this :

    insert into table1 (id, serial_no) select ‘asd’ as id, count(name) as serial_no from where category=’blah’

  8. Moazzam says:

    It won’t let me edit my comment so I am posting a new one. I had an error in the query I posted. Here is the right one :

    insert into table1 (id, serial_no) select ‘asd’ as id, count(name) as serial_no from table1 table1_1 where category=’blah’

  9. peter says:

    Moazzam,

    Please report it as a but KILL for the query should not cause data corruption. It would be OK to abort the query and have partially executed insert for MyISAM tables but if index gets corrupted it is surely a bug.

Speak Your Mind

*