Bug #18260 mysqldumpslow doesn't properly handle multi-row inserts/updates
Submitted: 15 Mar 2006 17:08 Modified: 16 Mar 2006 9:21
Reporter: Olaf van der Spek (Basic Quality Contributor) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: mysqldump Command-line Client Severity:S4 (Feature request)
Version:5.0.18 OS:Linux (Debian)
Assigned to: CPU Architecture:Any

[15 Mar 2006 17:08] Olaf van der Spek 
Description:
Hi,

My mysqldumpslow output contains tons of screens full of 
insert into xcl_players (rank, pid) values (N,N),(N,N),(N,N),(N,N),(N,N),(N,N),(N,N),(N,N),(N,N) on duplicate key update rank = values(rank)
I think it should aggregate these to for example
insert into xcl_players (rank, pid) values (N,N)[] on duplicate key update rank = values(rank)

How to repeat:
-
[16 Mar 2006 9:14] Hartmut Holzgraefe 
i have changed the severity to "feature request", i'm not really sure whether this 
is going to happen though as the idea of the different log files, including the slow
log, is to log a query "as is" so far ...

maybe its better to just not log INSERTS at all as a long enough multi-insert
is expected to be slow ...
[16 Mar 2006 9:21] Olaf van der Spek 
> is going to happen though as the idea of the different log files,
> including the slow log, is to log a query "as is" so far ...

You already replace values by N. If you prefer, you can make the use of [] optional.
Not logging at multi-row inserts at all is not a good idea IMO.
[17 Oct 2007 15:51] Nils Goroll 
see Bug #7414 for a fix