https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35687
Emily Lamancusa <emily.lamanc...@montgomerycountymd.gov> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |emily.lamancusa@montgomeryc
| |ountymd.gov
--- Comment #13 from Emily Lamancusa <emily.lamanc...@montgomerycountymd.gov>
---
I can't recreate either...but I wonder if it has something to do with the
sql_mode? I can't seem to find or remember where it's configured, but if I
recall correctly, the dev environment is set to strict mode, and production
environments usually aren't, right?
This page https://bugs.mysql.com/bug.php?id=93838 indicates that trying to make
a nullable column non-nullable will actually succeed in strict mode but throw a
"cannot change column used in foreign key constraint" in non-strict mode. (The
logic being that, in non-strict mode, null values will be filled with a default
value that may violate the foreign key constraint, whereas in strict mode the
command will not be allowed to execute if there are any existing null values in
the data.)
Maybe adding a primary key follows the same logic, and will fail only in
non-strict mode?
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
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/
