[
https://issues.apache.org/jira/browse/NETBEANS-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221608#comment-17221608
]
Matthias Bläsing commented on NETBEANS-3823:
--------------------------------------------
I found the reason. From the SQL Script:
{code:sql}
CREATE TABLE IF NOT EXISTS `plugin` (
-- ...
`last_updated_at` datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE
CURRENT_TIMESTAMP,
-- ...
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_czech_ci;
{code}
This means, that any update of the plugin table causes the `last_updated_at`
column of the affected row to be set to the current timestamp.
One such event is a download. A download causes the `download` column to be
incremented, which will cause an update of `last_updated_at` in the DB.
> At update center "Latest updates" has suspicious dates.
> -------------------------------------------------------
>
> Key: NETBEANS-3823
> URL: https://issues.apache.org/jira/browse/NETBEANS-3823
> Project: NetBeans
> Issue Type: Bug
> Components: updatecenters - Pluginportal
> Reporter: Ernie Rael
> Assignee: Matthias Bläsing
> Priority: Minor
>
> I'm not entirely certain, but pretty sure that in the "Latest updates" list
> the dates associated with specific plugins are not accurate.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
