This patch caused Evergreen to break. After applying the patch, the Evergreen database couldn't get new rows created. Postgres complains about having null values on non-null columns. The test I used was creating a new Org Unit. This is the Postgres log message:
ERROR: null value in column "shortname" violates not-null constraint
INSERT INTO actor.org_unit (billing_address,holds_address,id,ill_address,mailing_address,name,ou_type,parent_ou,shortname,email,phone,opac_visible,fiscal_calendar) VALUES (DEFAULT,DEFAULT,DEFAULT,DEFAULT,DEFAULT,DEFAULT,2,1,DEFAULT,DEFAULT,DEFAULT,'f',1);
I'm not exactly sure what part of this patch causes this cascading issue.
All,
This patch caused Evergreen to break. After applying the patch, the Evergreen database couldn't get new rows created. Postgres complains about having null values on non-null columns. The test I used was creating a new Org Unit. This is the Postgres log message:
ERROR: null value in column "shortname" violates not-null constraint
INSERT INTO actor.org_unit (billing_ address, holds_address, id,ill_ address, mailing_ address, name,ou_ type,parent_ ou,shortname, email,phone, opac_visible, fiscal_ calendar) VALUES (DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, DEFAULT, 2,1,DEFAULT, DEFAULT, DEFAULT, 'f',1);
I'm not exactly sure what part of this patch causes this cascading issue.
I'm using this patch:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ sandbergja/ lp1879517_ alternative_ patch