[Rt-commit] rt branch, 5.0-trunk, updated. rt-5.0.0alpha1-117-g32a70d92cf

[? sunnavy]

The branch, 5.0-trunk has been updated
       via  32a70d92cfefda4ebcf0c33c63b510669de1e865 (commit)
       via  7c747ab85f4b42d7a6b9253f65e253a6b75045df (commit)
       via  23c7e900dfffe0202aef4682c9e0ae5af03f16d0 (commit)
      from  5426bad310405cd92c74f57d1113f46e15ec2004 (commit)

Summary of changes:
 docs/UPGRADING-5.0              | 27 ++++++++++++++++++++++-----
 etc/upgrade/4.5.4/schema.Oracle |  4 +---
 etc/upgrade/4.5.4/schema.Pg     |  4 +---
 etc/upgrade/4.5.4/schema.mysql  |  4 +---
 4 files changed, 25 insertions(+), 14 deletions(-)

- Log -----------------------------------------------------------------
commit 7c747ab85f4b42d7a6b9253f65e253a6b75045df
Author: Jim Brandt <jbrandt at bestpractical.com>
Date:   Thu Apr 9 14:13:58 2020 -0400

    Document disk space needs for DB upgrade

diff --git a/docs/UPGRADING-5.0 b/docs/UPGRADING-5.0
index 64b533f828..54c15e23ed 100644
--- a/docs/UPGRADING-5.0
+++ b/docs/UPGRADING-5.0
@@ -36,16 +36,33 @@ changes made directly to the RT code, it's a good time to look at the hooks
 RT provides for custom code in extensions or in the local directory. See
 F<docs/writing_extensions.pod> for more information.
 
-=head2 Notable Changes
+=head2 Database Changes
 
 =over
 
 =item *
 
-On MySQL and MariaDB, the default character set has been changed from
-utf8 to utf8mb4. This provides support for 4-byte characters such as
-emojis on tickets. Postgres and Oracle already had support for these
-characters and are not effected by this update.
+For MySQL and MariaDB, the default character set has been updated to utf8mb4
+to accommodate more unicode characters including emojis. See F<README.MySQL>
+and F<README.MariaDB> for details.
+
+=item *
+
+The Id field in some tables is changed from INT to BIGINT to accommodate
+large RT systems that may hit the maximum number of ids. Because this
+change touches large RT tables like Transactions and Attachments, this
+upgrade step may take a while to run.
+
+You also will need free disk space equal to the size of these tables
+while running because MySQL, MariaDB, and Postgres will create a
+temporary copy of the table while running. If you don't have sufficient
+space, it can cause this step to fail.
+
+=back
+
+=head2 Notable Changes
+
+=over
 
 =item *
 

commit 32a70d92cfefda4ebcf0c33c63b510669de1e865
Merge: 5426bad310 7c747ab85f
Author: sunnavy <sunnavy at bestpractical.com>
Date:   Sat Apr 25 04:01:32 2020 +0800

    Merge branch '5.0/merge-attachments-schema-changes' into 5.0-trunk


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