https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23673 --- Comment #18 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to Tomás Cohen Arazi from comment #17)
(In reply to Jonathan Druart from comment #16)
(In reply to Agustín Moyano from comment #14)
Hi Jonathan
1. Should not we have the new column with the "default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP" clause in order to delegate the update of this value to the DBMS?
Mysql doesn't accept a table with 2 columns with "default CURRENT_TIMESTAMP".. there can be only one.
Hola Agustín, Yes I know and that's why I suggested to have it on the new column :)
Take a look at library_groups or borrowers tables for instance. Note that article_requests does the reverse.
You mean making the 'time_queued' column TIMESTAMP DEFAULT NULL (and so making us set it manually), and making 'updated_on' be the one with the trigger? (so we don't do the update manually?). I'm fine with either. Just trying to clarify so we move this forward.
Yes, that is what I meant. 4252 created_on TIMESTAMP NULL, -- Date and time of creation 4253 updated_on TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, -- Date and time of last -- You are receiving this mail because: You are watching all bug changes.