Difference between revisions of "Oracle Databases and Email Subscriptions"
(Created page with "Category:How_To Fusion Registry Version 1.3 (due to be released in August 2025) contains a change to the way email addresses (entered and stored during the Email Subscript...") |
|||
| Line 1: | Line 1: | ||
[[Category:How_To]] | [[Category:How_To]] | ||
| − | Fusion Registry Version 1.3 ( | + | Fusion Registry Version 1.3 (released in August 2025) contains a change to the way email addresses (entered and stored during the Email Subscription process) are handled in Oracle databases. |
Previously, in the Fusion Registry 11 series and subsequent versions, it was possible to have duplicate emails stored in the Oracle database which was resulting in multiple notifications being sent for the same event. | Previously, in the Fusion Registry 11 series and subsequent versions, it was possible to have duplicate emails stored in the Oracle database which was resulting in multiple notifications being sent for the same event. | ||
Latest revision as of 01:55, 12 November 2025
Fusion Registry Version 1.3 (released in August 2025) contains a change to the way email addresses (entered and stored during the Email Subscription process) are handled in Oracle databases.
Previously, in the Fusion Registry 11 series and subsequent versions, it was possible to have duplicate emails stored in the Oracle database which was resulting in multiple notifications being sent for the same event.
Once R1.3 is installed, new subscriptions will be converted to lower case email addresses and duplicated emails will not be allowed.
Email subscriptions made prior to Version 1.3 will not be affected (so duplicates may exist in the database table) however, if the subscription is changed (for example a new subscription to a different event) the system will perform the remove duplicate process.
