Bug 23463: (follow-up 3) Fix timestamp default value
authorJonathan Druart <jonathan.druart@bugs.koha-community.org>
Mon, 23 Mar 2020 16:21:24 +0000 (17:21 +0100)
committerMartin Renvoize <martin.renvoize@ptfs-europe.com>
Tue, 31 Mar 2020 08:52:57 +0000 (09:52 +0100)
commit9c383aa286fee5a29c6f084873f2eb6644bad64f
tree0cc47637ffbbfd96adf2b8ffa79c8544c651dd94
parentaf1275ce7d285aaf179f9d25403b5a578b4f0d01
Bug 23463: (follow-up 3) Fix timestamp default value

This is the only situation I found where:
 * t/db_dependent/Koha/Item.t is passing
 * t/db_dependent/Koha/Object.t is passing
 * MySQL 8 is happy (and not fail with "Column 'timestamp' cannot be null"), which is certainly what I missed in the previous follow-up

About the change to Object.t: the next store was called without the
generated timestamp, so it is needed to call discard_changes.

Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Koha/Item.pm
Koha/Object.pm
t/db_dependent/Koha/Object.t