DB Patch

[tom123]

I think that DB patches should be managed differently.
Actually, is impossibile to create custom paches, because when a new ISPConfig release will be available, your patch will overwrite the custom ones.

I think that you should create a 'custom' directory where developers can add own patches, that will be run after yours.

For example:

/sql/incremental/upd_0020.sql
/sql/incremental/upd_0020.sql
/sql/incremental/custom/upd_0002.sql
/sql/incremental/custom/upd_0003.sql

or, maybe better:

/sql/incremental/upd_0052.sql
/sql/incremental/upd_0053.sql
/sql/incremental/custom_0012.sql
/sql/incremental/custom_0013.sql

[till]

If you would contribute improvements back to the ispconfig main svn like the other devs are do it and as its common with OS projects, then you dont need custom patches.