https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37592
--- Comment #21 from Paul Derscheid <[email protected]> --- Created attachment 174968 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=174968&action=edit Bug 37592: (QA follow-up) Update db_rev to align DBIx::Class with database schema for creation_date, modification_date - DBIx::Class appears to determine column nullability based on database metadata. When columns are added via `ALTER TABLE` without explicitly specifying `NOT NULL`, the metadata may indicate `IS_NULLABLE = "YES"`, causing DBIx::Class to generate `is_nullable => 1` in the schema files. This behavior might not account for the implicit `NOT NULL` enforcement of `DEFAULT CURRENT_TIMESTAMP`. - Adding `NOT NULL` explicitly in the `ALTER TABLE` statements ensures the database metadata reflects the intended constraints, potentially resolving this issue. - Additionally, comments in the atomic update and `kohastructure.sql` are aligned for consistency and clarity. -- 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/
