[
https://issues.apache.org/jira/browse/VCL-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059723#comment-16059723
]
ASF subversion and git services commented on VCL-1053:
------------------------------------------------------
Commit 1799598 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1799598 ]
VCL-1053 - Prepare VCL 2.5 release
update-vcl.sql: modified procedure moveConnectMethodPortProtocol: added "WHERE
port != 0" to last INSERT statement to handle upgrades from VCL versions
without any connectmethod tables. I saw a problem upgrading from 2.2.2 where it
caused 3 entries to be inserted with port set to 0. Then, a later query in the
update-vcl.sql script caused 3 more entries to be inserted with the correct
port numbers resulting in 2 entries for each connect method with one having the
right port and one having 0.
> Prepare VCL 2.5 release
> -----------------------
>
> Key: VCL-1053
> URL: https://issues.apache.org/jira/browse/VCL-1053
> Project: VCL
> Issue Type: Bug
> Components: database, vcld (backend), web gui (frontend)
> Reporter: Andy Kurth
> Fix For: 2.5
>
>
> This issue is to track all of the VCL 2.5 release preparation tasks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
