Recovery from binlog

[Adam Warnowski]

I have problem with recovery from binlog. I have done:
mysqlbinlog -v --base64-output=DECODE-ROWS log_file
Inside generated I see something like:
### UPDATE test.t
### WHERE
### @1=1
### @2='apple'
### @3=NULL
### SET
### @1=1
### @2='pear'
### @3='2009:01:01'
So it is impossible to import this file. Please help if I should use some utils which converts me this to sql:
UPDATE test.t SET col1=1, col2='pear', col3=2009:01:01' WHERE col1 = 1;

or maybe there is switch to use with mysqlbinlog which generates normal sql's.
In some lines of output I see normal UPDATEs. I don't know what it depends on.