This is a catchall issue to track database changes for VCL 2.4 which aren't directly related to another issue.
We really need to rework the database update process when upgrading VCL versions. update-vcl.sql is difficult to manage and keep in sync with vcl.sql. A single Perl script could be written which could be used for both fresh installs and updates.
For fresh installs, it could simply import the vcl.sql file.
For updates, it could query the existing database in order to determine if table definitions match vcl.sql and then execute an "alter" statement. This will be much easier to code than the current stored procedures in update-vcl.sql.