Created attachment 15774 [details] [review]
Proposed patch

See commit comment

This shouldn't be needed

Can you check your database structure, it should be
`timestamp` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP,

Which means MySQL will update it, can you do show create table biblio;

select biblionumber,title,timestamp from biblio;
+--------------+---------+---------------------+
| biblionumber | title   | timestamp           |
+--------------+---------+---------------------+
|            1 | chris   | 2012-07-01 16:21:13 |
|            2 | chris 2 | 2012-06-11 23:14:39 |
+--------------+---------+---------------------+

 update biblio set title='test timestamp' where biblionumber=1;
Query OK, 1 row affected (0.05 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> select biblionumber,title,timestamp from biblio;
+--------------+----------------+---------------------+
| biblionumber | title          | timestamp           |
+--------------+----------------+---------------------+
|            1 | test timestamp | 2013-03-01 22:59:09 |
|            2 | chris 2        | 2012-06-11 23:14:39 |
+--------------+----------------+---------------------+
2 rows in set (0.00 sec)

Your right Chris,
I did not knew this behavior.
On a biblio edition : biblioitems.timestamp is always updated (because marcxml and marc are updated), but biblio.timestamp is updated only if a concerned column is updated (title, author, ...).

Closed.