@@ -9,15 +9,24 @@ then follow these steps:
991) 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) Add your ALTER TABLE, or if it is a complete new table then the add table,
13- statement(s) in MySQL syntax which is/are required to modify the current
14- ispconfig database during update to the file upd_dev_collection.sql in the
15- sql/incremental subfolder.
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.
1624
17- Please do not create new patch sql files as those will be generated on
18- new releases from the upd_dev_collection.sql file. Also please do not
19- modify older (already released) patch files, they will not get executed
20- again if the update was already run once on a system.
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)
27+ patch files, they will not get executed again if the update was already run
28+ once on a system, and will result in missing updates on any system where they
29+ have not run yet.
2130
2231 After a patch has been executed, the dbversion field in the server table gets
2332 increeased to the version number of the last installed patch.
0 commit comments