[
https://issues.apache.org/jira/browse/VCL-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295446#comment-14295446
]
ASF subversion and git services commented on VCL-764:
-----------------------------------------------------
Commit 1655401 from [~arkurth] in branch 'vcl/trunk'
[ https://svn.apache.org/r1655401 ]
VCL-764
Added command to remove constraint on sublog.blockRequestid in update-vcl.sql.
This should only exist in the database if the schema was created or updated
from the schema files in trunk between 2.3.2 and 2.4.
> Database changes for VCL 2.4
> ----------------------------
>
> Key: VCL-764
> URL: https://issues.apache.org/jira/browse/VCL-764
> Project: VCL
> Issue Type: Improvement
> Components: database
> Affects Versions: 2.3.2
> Reporter: Andy Kurth
> Fix For: 2.4
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
