[
https://issues.apache.org/jira/browse/VCL-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393104#comment-14393104
]
ASF subversion and git services commented on VCL-763:
-----------------------------------------------------
Commit 1670950 from [~jfthomps] in branch 'vcl/trunk'
[ https://svn.apache.org/r1670950 ]
VCL-763 - Add missing constraints to database tables
blockallocations.php:
-modified AJtoggleBlockTime - if setting skip from 1 to 0 in database, also set
processed to 0 in case the blockTime had been processed already. Otherwise,
when skip is set to 0, if the block time had been prevously processed, it will
not get processed again (and what had been set up by the previous processing
would have been undone when skip was set to 1)
-modified processBlockAllocationInput: if $return['groupid'] == 0, set it to
'NULL' so when it is used for an insert or update, it will be NULL instead of 0
utils.php: modified checkClearImageMeta - added check for query that gets
existing imagemeta entry returning no rows - this can happen if the imagemeta
entry is due to subimages, and someone deletes the subimages and then updates
the image profile, in which case the deleting of the subimages will remove the
imagemeta entry, but the continuation for editing the image profile will still
have the imagemetaid
> Add missing constraints to database tables
> ------------------------------------------
>
> Key: VCL-763
> URL: https://issues.apache.org/jira/browse/VCL-763
> Project: VCL
> Issue Type: Improvement
> Components: database
> Affects Versions: 2.3.2
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Priority: Minor
> Fix For: 2.4
>
>
> There are some database columns which reference another table which are
> missing a constraint. One example is computer.vmhostid. It's handy to have
> the constraints defined.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
