diff options
author | Francesco Borzì <borzifrancesco@gmail.com> | 2024-11-15 11:27:45 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-11-15 11:27:45 +0100 |
commit | c5ae1ae88fd2a76e119e54cd896d0227f703117c (patch) | |
tree | 4b965879c8a513a36088e32f1001131c98b8019a /data/sql/base/database-squash.md | |
parent | 6a25a1d1a71f6aed87f8c021de319c16d992eb8a (diff) |
chore(DB): move 2023 update files (#20470)
* chore(DB): move 2023 update files
* chore: flag files as archied
Diffstat (limited to 'data/sql/base/database-squash.md')
-rw-r--r-- | data/sql/base/database-squash.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/data/sql/base/database-squash.md b/data/sql/base/database-squash.md index 3275e727f6..a09a9a8f8a 100644 --- a/data/sql/base/database-squash.md +++ b/data/sql/base/database-squash.md @@ -3,9 +3,11 @@ New routines around handling database squashes since https://github.com/azerothc > [!CAUTION] > These steps are only for project maintainers who intend to update base files. -We ONLY squash into BASE files. We never move files. -ARCHIVE dir is UNUSED. -All update files ALWAYS exist in the updates dir. +During the DB squash procedure, we do NOT move files. +The archive dir is NO longer used as part of the DB squash procedure, +but simply as a place where to move update files when they get too many. + +Moving files to the archive folder is NOT part of the squash procedure anymore. as the `updates` table in base files always will contain the entries from the updates dir they will never be run again on a clean setup. |