Skip to content

Commit 09cf5d6

Browse files
committed
update sql patch instructions. fixes #5630
1 parent f42ab5a commit 09cf5d6

File tree

1 file changed

+16
-10
lines changed

1 file changed

+16
-10
lines changed

install/sql/README.txt

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -9,18 +9,24 @@ then follow these steps:
99
1) Add the field or table in the ispconfig3.sql file. This file contains the
1010
complete database dump which is used when ISPConfig gets installed.
1111

12-
2) Create a new file in the "incremental" subfolder wich contains the alter
13-
table, or if it is a complete new table then the add table, statement(s) in
14-
MySQL syntax which is/are required to modify the current ispconfig database
15-
during update. The naming scheme of the sql patch update files is
16-
upd_0001.sql, upd_0002.sql, upd_0003.sql etc. Ensure that the number that
17-
you choose for the new file is a +1 increment of the number of the last
18-
existing file and that the number is formatted with 4 digits.
12+
2) Edit the file "incremental/upd_dev_collection.sql" which contains the SQL
13+
statements (alter table, add table, update, etc.) in MySQL syntax which
14+
are required to modify the current ispconfig database during update.
15+
16+
The upd_dev_collection.sql file contains all db schema modifications
17+
for changes made since the last ISPConfig release. If SQL statements
18+
are already present in the file when you make your additions, add yours
19+
to the end of the file, and do not remove any existing statements.
20+
21+
When a new ISPConfig update is released, the contents of
22+
upd_dev_collections.sql will move to an sql patch file, using the naming
23+
scheme upd_0001.sql, upd_0002.sql, upd_0003.sql etc.
1924

20-
A patch file may contain one or more alter table statements. Every patch file
21-
gets executed once in the database, so do not modify older (already released)
25+
A patch file may contain one or more SQL modification statements. Every patch
26+
file gets executed once in the database, so do not modify older (already released)
2227
patch files, they will not get executed again if the update was already run
23-
once on a system.
28+
once on a system, and will result in missing updates on any system where they
29+
have not run yet.
2430

2531
After a patch has been executed, the dbversion field in the server table gets
2632
increeased to the version number of the last installed patch.

0 commit comments

Comments
 (0)