[jira] [Commented] (VCL-764) Database changes for VCL 2.4

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/VCL-764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353174#comment-14353174 ] 

ASF subversion and git services commented on VCL-764:
-----------------------------------------------------

Commit 1665294 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1665294 ]

VCL-764 - Database changes for VCL 2.4

update-vcl.sql: modified AddConstraintIfNotExists: extended to accept 'nullCASCADE' for constraintAction with constraintType is both; this causes the constraint to be set as "ON DELETE SET NULL ON UPDATE CASCADE"; modified constraint for image.imagemetaid to call AddConstraintIfNotExists with nullCASCADE for constraintAction so things will match what is in vcl.sql (and allow entries in imagemeta to be deleted)

> 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)