Details
-
Bug
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
customfield_11100 41974
-
Folijet Sprint 105, Folijet Sprint 106
-
1
-
Folijet
-
R1 2021
-
High
Description
When an environment is upgraded from Goldenrod-Hotfix-5 to Honeysuckle, the below function is present
CREATE FUNCTION set_id_in_jsonb () RETURNS trigger AS $$ BEGIN NEW.jsonb = jsonb_set(NEW.jsonb, '{id}', to_jsonb(NEW.id)); RETURN NEW; END; $$ LANGUAGE 'plpgsql' COST 100; ALTER FUNCTION set_id_in_jsonb () OWNER TO folio;
where as on a fresh install of Honeysuckle, it isn't - so probably it isn't being used but a migration script needs to be written for it to be dropped.
I did observe https://github.com/folio-org/mod-source-record-storage/blob/3970630d2c02fa2674d390d34ebac13fd81442a5/mod-source-record-storage-server/src/main/resources/liquibase/tenant/scripts/v-0.0.2/2020-06-13--17-00-drop-unused-functions.xml#L81 but probably versions need to be checked for when it needs to be dropped.
Version of mod-source-record-storage in Goldenrod-hotfix-5 -> 4.0.4
Honeysuckle version upgraded to -> 4.1.3
Fresh Honeysuckle installation version -> 4.1.3
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-2614 NFR: Data Import (Batch Importer for Bib Acq) & PubSub R1 2021 Technical, NFR, & Misc bug work
-
- Closed
-
- relates to
-
MODSOURCE-349 Function set_id_in_jsonb is present in migrated Juniper/Kiwi environment - Lotus BF
-
- Closed
-
-
MODSOURCE-491 Function set_id_in_jsonb is present in migrated Juniper/Kiwi environment - Morning Glory
-
- Closed
-