https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27253
--- Comment #6 from Marcel de Rooy <[email protected]> --- (In reply to Kyle M Hall from comment #0) > Simply put, the borrowers table column updated_on in kohastructure.sql > specifies that it cannot be null, but the updatedatabase.pl it can. It > appears the NOT got lost when the column as renamed 'updated_on' from > 'timestamp' in a followup on bug 10459. > > Fixing it is easy, the question is, what do we do with currently NULL > updated_on's? My though is to set them to the unix epoch ( 1970-01-01 ). (In reply to Jonathan Druart from comment #1) > What about MAX(date_renewed, dateenrolled, last_seen)? I think it is an arbitrary choice. For my part NOW() would have been good either (and much easier). After all, we are updating those borrowers .. now, right? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
