From 3f25f6c677ab5a3d567db5622134bf18c95169c9 Mon Sep 17 00:00:00 2001 From: Jason Etheridge Date: Thu, 6 Aug 2020 13:54:13 -0400 Subject: [PATCH] lp1846354 add a WARNING to the release notes about the auditor table Signed-off-by: Jason Etheridge --- .../Client/lp1846354_consolidate_patron_notes.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/RELEASE_NOTES_NEXT/Client/lp1846354_consolidate_patron_notes.adoc b/docs/RELEASE_NOTES_NEXT/Client/lp1846354_consolidate_patron_notes.adoc index 0bd1febd14..0d2f9cab95 100644 --- a/docs/RELEASE_NOTES_NEXT/Client/lp1846354_consolidate_patron_notes.adoc +++ b/docs/RELEASE_NOTES_NEXT/Client/lp1846354_consolidate_patron_notes.adoc @@ -11,3 +11,10 @@ The underlying data structure has also changed with all notes living in the acto And for actor.usr_message, there is now both a pub column and a deleted column. Depending on privacy policies, system adminstrators may wish to set up a recurring process to truly delete older entries in actor.usr_message that have been flagged as deleted. + +WARNING: The upgrade script will remote the alert_message field from the auditor table, so if you care about preserving those you should run a query to create a backup. + +For example: + +[source,sql] +CREATE TABLE auditor.backup_usr_alert_msg AS CREATE audit_id, audit_time, audit_action, audit_user, audit_ws, id as "usr_id", last_update_time, alert_message FROM auditor.actor_usr_history WHERE alert_message IS NOT NULL; -- 2.11.0