[Koha-bugs] [Bug 21219] NULL values in updated_on field break the Patrons REST API

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21219

--- Comment #2 from Pete Edwards <koha at jsense.co.uk> ---
I did wonder whether it could be an update issue but I couldn't find any
evidence of a script that would have set a value on the column for existing
records when the column was added. Does simply changing the column definition
to "NOT NULL" cause the default timestamp to be set - if so I really don't
understand why it was created with "NULL".

Obviously, this leaves me concerned that there could be other other
discrepancies - is there an easy way to compare my actual schema to the one the
should be installed - I installed v18.05 but my database has the column defined
as:

  `updated_on` timestamp NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE
CURRENT_TIMESTAMP,

Thanks

-- 
You are receiving this mail because:
You are watching all bug changes.