Incorrect datatype for Default Record Match Set org setting
Bug #1552861 reported by
Jeff Davis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Low
|
Unassigned | ||
2.11 |
Fix Released
|
Low
|
Unassigned |
Bug Description
This bug affects Evergreen 2.4.0 through master.
Bug 1067087 introduced a new org setting, Default Record Match Set (vandelay.
It's easy enough to fix this in 950.data.
Changed in evergreen: | |
milestone: | none → 2.next |
tags: | added: pullrequest vandelay |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Pushed a schema fix to working branch user/jeffdavis/ lp1552861- default- match-set- datatype:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=commitdif f;h=23ad642
I'm not sure how to go about protecting existing values. If they correspond to existing vandelay. match_set. id values, then all is well, but what if they don't? Do we give a warning and wipe invalid values, try to match on vandelay. match_set. name, or...? (As noted above, invalid values already don't work.)