aboutsummaryrefslogtreecommitdiff
path: root/sqlite/z-001-migrate-v01-to-v02.sql
diff options
context:
space:
mode:
authorfusion32 <marcopuzziello@gmail.com>2025-10-23 04:26:11 -0300
committerfusion32 <marcopuzziello@gmail.com>2025-10-23 04:26:11 -0300
commit27a0df43b33b712462ab5be65462162b9e4bcd29 (patch)
treee9170746ecae5c8689e16750e6ffa5c6e339d25d /sqlite/z-001-migrate-v01-to-v02.sql
parent0ff6217227ce551d6c91524c8e7fd37352e20490 (diff)
downloadquerymanager-27a0df43b33b712462ab5be65462162b9e4bcd29.tar.gz
querymanager-27a0df43b33b712462ab5be65462162b9e4bcd29.zip
change how guild data is stored
Diffstat (limited to 'sqlite/z-001-migrate-v01-to-v02.sql')
-rw-r--r--sqlite/z-001-migrate-v01-to-v02.sql6
1 files changed, 3 insertions, 3 deletions
diff --git a/sqlite/z-001-migrate-v01-to-v02.sql b/sqlite/z-001-migrate-v01-to-v02.sql
index 19fdddb..a874194 100644
--- a/sqlite/z-001-migrate-v01-to-v02.sql
+++ b/sqlite/z-001-migrate-v01-to-v02.sql
@@ -2,10 +2,10 @@
-- must be manually executed as `sqlite3 -bail -echo tibia.db < migration.sql`
-- because the original schema didn't have a `Patches` table which is necessary
-- with the new automatic patching system. Future migration scripts can be placed
--- in `patches/` for automatic execution but not this one, unfortunately.
+-- in `patches/` for automatic execution but not this one, unfortunately. For
+-- more details see `sqlite/README.txt`.
-- These changes are already present in the latest `schema.sql`, so trying to
--- apply it to a newly created database will result in errors. For more details
--- see `sqlite/README.txt`.
+-- apply them to a newly created database will result in errors.
--==============================================================================
BEGIN;