You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/01/31 16:06:00 UTC
[jira] [Commented] (VCL-1111) statgraphcache table not correctly
being used
[ https://issues.apache.org/jira/browse/VCL-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757413#comment-16757413 ]
ASF subversion and git services commented on VCL-1111:
------------------------------------------------------
Commit 9c7c26ea18792008f7c599c6d90a067a0dc30273 in vcl's branch refs/heads/develop from Josh Thompson
[ https://gitbox.apache.org/repos/asf?p=vcl.git;h=9c7c26e ]
VCL-1111 - statgraphcache table not correctly being used
statistics.php: modified getStatGraphDayData, getStatGraphDayConUsersData, getStatGraphConBladeUserData, and getStatGraphConVMUserData: modified query to allow for provisioningid to be NULL or 0 if searching for any provisioningid
> statgraphcache table not correctly being used
> ---------------------------------------------
>
> Key: VCL-1111
> URL: https://issues.apache.org/jira/browse/VCL-1111
> Project: VCL
> Issue Type: Bug
> Components: web gui (frontend)
> Reporter: Josh Thompson
> Priority: Minor
> Fix For: 2.5.1
>
>
> There is a table in the database for caching computed values so that they don't have to be computed every time the data is needed for a graph. Values are only saved to it once they wouldn't be changed. There was a foreign key change change in a previous release that changed the provisioningid field in this table from being 0 to NULL which broke queries that select data from the table. The queries needs to be updated to account for the change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)