[Koha-bugs] [Bug 27253] New: borrowers.updated_on cannot be null on fresh install, but can be null with upgrade

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

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

            Bug ID: 27253
           Summary: borrowers.updated_on cannot be null on fresh install,
                    but can be null with upgrade
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5 - low
         Component: Architecture, internals, and plumbing
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: kyle at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org

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 ).

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