[Rt-commit] rt branch, unique-group-names, updated. rt-3.9.4-532-g2a360e4

[Thomas Sibley]

The branch, unique-group-names has been updated
       via  2a360e4f96b6a4fb62b364e6dea9b977b51b5f9a (commit)
      from  d477e02f12a787e244181b02f17b1a79e95f5212 (commit)

Summary of changes:
 UPGRADING |   16 +++++++++++++++-
 1 files changed, 15 insertions(+), 1 deletions(-)

- Log -----------------------------------------------------------------
commit 2a360e4f96b6a4fb62b364e6dea9b977b51b5f9a
Author: Thomas Sibley <trs at bestpractical.com>
Date:   Fri Nov 19 11:59:04 2010 -0500

    Add upgrading information about unique group names

diff --git a/UPGRADING b/UPGRADING
index 5ddf803..58eb94d 100644
--- a/UPGRADING
+++ b/UPGRADING
@@ -20,7 +20,6 @@ well.
 
 
 *******
-
 UPGRADING FROM RT 3.8.x - Changes:
 
 The deprecated classes RT::Action::Generic, RT::Condition::Generic and RT::Search::Generic
@@ -37,6 +36,21 @@ with
 
     { $Ticket->SubjectTag }
 
+* Unique names are now enforced for user defined groups.  New groups cannot be
+  created with a duplicate name and existing groups cannot be renamed to an
+  in-use name.  The admin interface will warn about existing groups with
+  duplicate names.  Although the groups will still function, some parts of the
+  interface (rights management, subgroup membership) may not work as expected
+  with duplicate names.  Running
+
+    /opt/rt3/sbin/rt-validator --check
+
+  will report duplicate group names, and running it with --resolve will fix
+  duplicates by appending the group id to the name.
+
+  Nota Bene: As a result of differing indexes in the schema files, Postgres and
+  SQLite RT databases have enforced group name uniqueness for many years at the
+  database level.
 
 *******
 UPGRADING FROM 3.8.8 and earlier - Changes:

-----------------------------------------------------------------------