aboutsummaryrefslogtreecommitdiff
path: root/sqlite/z-001-migrate-v01-to-v02.sql
diff options
context:
space:
mode:
authorfusion32 <marcopuzziello@gmail.com>2025-10-18 02:32:59 -0300
committerfusion32 <marcopuzziello@gmail.com>2025-10-18 02:35:24 -0300
commit601ce32ee8d0cee32b66c87b0bfefa7424a5b8c8 (patch)
tree7b06c2d9d385b957377b801b83f004fc554e19d0 /sqlite/z-001-migrate-v01-to-v02.sql
parentd92f642810dc3125515d64f953d2bee840de1cc1 (diff)
downloadquerymanager-601ce32ee8d0cee32b66c87b0bfefa7424a5b8c8.tar.gz
querymanager-601ce32ee8d0cee32b66c87b0bfefa7424a5b8c8.zip
modify how automatic SQLite patches/upgrades works + overall cleanup
Diffstat (limited to 'sqlite/z-001-migrate-v01-to-v02.sql')
-rw-r--r--sqlite/z-001-migrate-v01-to-v02.sql14
1 files changed, 14 insertions, 0 deletions
diff --git a/sqlite/z-001-migrate-v01-to-v02.sql b/sqlite/z-001-migrate-v01-to-v02.sql
new file mode 100644
index 0000000..b7df053
--- /dev/null
+++ b/sqlite/z-001-migrate-v01-to-v02.sql
@@ -0,0 +1,14 @@
+-- NOTE(fusion): This file contains the migration script from v0.1 to v0.2. It
+-- can be placed into `patches/` to upgrade an existing database. Note that these
+-- changes are already present in the latest `schema.sql`, so trying to patch a
+-- newly created database will probably result in errors. See `sqlite/README.txt`
+-- for more details.
+--==============================================================================
+
+ALTER TABLE Worlds RENAME COLUMN OnlineRecord TO OnlinePeak;
+ALTER TABLE Worlds RENAME COLUMN OnlineRecordTimestamp TO OnlinePeakTimestamp;
+ALTER TABLE CharacterRights RENAME COLUMN Right TO Name;
+
+ALTER TABLE Worlds ADD COLUMN LastStartup INTEGER NOT NULL DEFAULT 0;
+ALTER TABLE Worlds ADD COLUMN LastShutdown INTEGER NOT NULL DEFAULT 0;
+