https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37511
--- Comment #25 from Janusz Kaczmarek <[email protected]> --- (In reply to Katrin Fischer from comment #23) > Hi Janusz, > > to explain a bit more: > > In your DBIC schema changes file, that I dropped when pushing (as we usually > do), you have is_nullable = 0 (second patch) > > But when I regenerated the DBIC file running dbic after the database update, > it came out with is_nullable = 1 > > So: which one is correct? > If we want is_nullable = 0, we will probably need another database update > and kohastructure.sql change. Thank you for your explanation, Katrin. I have tried to retrace the process of preparing of my original schema changes and this time I got is_nullable = 1. No idea why in the original patch it was = 0... And I am pretty sure I did not correct the schema file by hand. As it is now (is_nullable = 1) seems totally correct and coherent with the table description in mysql. I am sorry for the confusion. And thank you for your patience. -- 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/
